Hacker GitHub

← All repos

w3c/webextensions

View on GitHub ↗ ★ 722 Bikeshed

Charter and administrivia for the WebExtensions Community Group (WECG)

46 mentions on Hacker News by 27 people: 2 stories, 44 comments · first 2021-06-05 · latest 2026-07-31

Mentions per year 46 mentions · busiest year 2023 (16)
20082026
  1. there's now a proposal for it https://github.com/w3c/webextensions/pull/1019/changes so it will probably appear eventually.
  2. …habits can still easily be collected from the combination of fingerprints and tracking URLs. https://github.com/w3c/webextensions/issues/302
    comment by krackers · 2025-07-12 · in Bypassing Google's big anti-adblock update
  3. This seems to be a significant problem: https://github.com/w3c/webextensions/issues/493#issuecomment... TL;DR: In order to detect ad blocks sites create "bait" URL's that look like ads, but are purely there to detect if ad blockers block…
    comment by rstuart4133 · 2024-08-15 · in Google pulls the plug on uBlock Origin
  4. …it in in terms of the API surface needed to properly support adblocking against a hostile web. https://github.com/w3c/webextensions/blob/56dc974e5d583d6989... https://github.com/w3c/webextensions/blob/01ac3748984f31885c...
  5. It sure is awfully convenient that MV3 by design will prevent referal-stripping extensions https://github.com/w3c/webextensions/issues/302 (By the way, the meeting minutes are all published so you can read exactly how they're conspiring to…
  6. That’s wrong: https://github.com/w3c/webextensions
  7. …also has the link to an issue in the webextensions repository indicating it's a limitation of MV3: https://github.com/w3c/webextensions/issues/112
  8. …to be able to be more alive than my agents. Yet my agents must all be dead. For shame, ye villains. https://github.com/w3c/webextensions/issues/139 This post definitely was quite a technical explanation. The opening framing, to me, means…
    comment by jauntywundrkind · 2023-11-25 · in There are no strings on me
  9. …have to have all behaviors predefined. I can't dial home & load my behaviors. Here's the issue, https://github.com/w3c/webextensions/issues/139 For a while it meant that userscripts didn't have any way to run. So Google introduced a new…
  10. …DNR is still not an acceptable replacement. There are still outstanding functionality gaps such as https://github.com/w3c/webextensions/issues/302 , which is interesting in that much of the tracking that privacy extensions are no longer…
  11. …various threats on the Web will be stuck in the past, unable to adapt as the threats evolve. [1] https://github.com/w3c/webextensions/issues/302 [2] https://www.eff.org/deeplinks/2021/12/googles-manifest-v3-st...
  12. …to innovate. The browser (Google) becomes the gatekeeper. And yes, we lose CNAME filtering.[1] https://github.com/w3c/webextensions/issues/151#issuecomment... Google is an advertising company. Chrome extensions already experienced a lost…
  13. …from the post may be that fixing tracking redirects is partially broken in Google’s Manifest V3: https://github.com/w3c/webextensions/issues/302 Google also happens to be a major link mangler and tracker. So, link cleaner (and generally…
  14. …we want the actual code of the extensions to be as reusable as (reasonably) possible. [1]: https://github.com/w3c/webextensions/
  15. …try to work out some open questions about where we're going and how we're going to get there. [1]: https://github.com/w3c/webextensions/ [2]: https://browserext.github.io/ [3]: https://www.w3.org/community/about/faq/ [4]:…
  16. …out what Firefox's limits are I came across this interesting issue on the W3C's webextensions repo: https://github.com/w3c/webextensions/issues/319 4 days ago the Chromium developers proposed upping the limit for certain types of…
  17. Yes, dynamic code is all outlawed. Disclaimer, I filed this issue. https://github.com/w3c/webextensions/issues/139
  18. …the web. And I absolutely hate it. Hate it hate it hate it hate it. Abominable way to hurt the web. https://github.com/w3c/webextensions/issues/139
  19. …API, the proposal has been merged into the WECG but the engineering work has not started yet." https://github.com/w3c/webextensions/blob/f8f430f1904c2a6fa8... MV2 is sticking around until at least 2024.
    comment by lapcat · 2023-04-01 · in Pausing Manifest V2 phase-out changes
  20. …a (non-complicated) extension recently and the service worker API seemed cleaner and modern. 1 https://github.com/w3c/webextensions/issues/72
  21. …API that allows to specify the position and size, and doesn't require any origin permissions. https://github.com/w3c/webextensions/issues/307
  22. …engineer at Apple working on extensions said that "Apple sees extension APIs as long term support". https://github.com/w3c/webextensions/issues/298#issuecomment...
    comment by dessant · 2023-01-14 · in Recent improvements to Safari
  23. …in MV3, but they haven't even started the implementation. They're still in the proposal phase. https://github.com/w3c/webextensions/issues/279
    comment by lapcat · 2022-12-09 · in Pausing Manifest V2 phase-out changes
  24. …are you doing? Earth to Google, what planet are you on? [1] Use cases not served by service workers https://github.com/w3c/webextensions/issues/72 [2] https://github.com/w3c/webextensions/issues/279#issuecomment...
  25. …much deeper, far more complicated fiasco of the highest & most critical importance to the web. [1] https://github.com/w3c/webextensions/issues/279 [2] https://github.com/w3c/webextensions/issues/134 [3]…
  26. https://github.com/w3c/webextensions/issues/264
  27. It looks like it's being worked on, see < https://github.com/w3c/webextensions/issues/279 >.
    comment by gorhill · 2022-09-23 · in Manifest V3, webRequest, and ad blockers
  28. …several very popular crbugs for how the web-based service workers don't work well for extensions ( https://github.com/w3c/webextensions/issues/72 ). Given all this, the Chrome team continues with the change citing increased performance…
    comment by gaurang_tandon · 2022-09-22 · in uBlock Origin Lite: Description
  29. …discussion in this area. [1]: https://www.w3.org/events/meetings/7bbba4a3-8305-45cd-a998-6... [2]: https://github.com/w3c/webextensions/pull/277 [3]: https://github.com/w3c/webextensions/blob/main/_minutes/2022... [4]:…
  30. …although details are scarce it seems MV4 will still retain JS code execution [1] [2]. [1]: https://github.com/w3c/webextensions/blob/main/_minutes/2022... (CTRL-F for "mv4") [2]: https://github.com/w3c/webextensions/blob/main/_minutes/2022.…
  31. ▲ 1
    The Charter of the WebExtensions Community Group (WECG)
    story by Trouble_007 · 2022-06-10 · 0 comments
  32. It's a superset of Chrome's functionality. E.g. https://github.com/w3c/webextensions/issues/134 . The Web Extension API in Firefox is generally a lot bigger than Chrome's, so there's plenty of differentiation and I wouldn't call it a clone.
  33. …github issue[2] on this. [1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... [2] https://github.com/w3c/webextensions/issues/139
  34. …good will to try to reduce them as much as possible. You can find some information about this here https://github.com/w3c/webextensions/tree/main/_minutes
  35. …same rule Apple uses to forbid v8 on iOS), & opened what I believe is the first issue against that. https://github.com/w3c/webextensions/issues/139 . The background tasks discussion is another important one: extensions no longer having…
  36. …extensions Let alone much more rewrites in exchange for probably-barely-usable extensions. [1]. https://github.com/w3c/webextensions/issues/72
  37. Manifest v3 is a shit show. https://github.com/w3c/webextensions/issues?q=is%3Aissue+is%...
  38. …A Mozillaian proposed a less limited Limited Events Page but Google has snubbed it & not discussed. https://github.com/w3c/webextensions/issues/134 Extensions are forced to use a small subset of JavaScript with no dynamic code execution.…
  39. …https://news.ycombinator.com/item?id=29425379 (freshly submitted) [2] https://github.com/w3c/webextensions/issues/72 [3] https://datatracker.ietf.org/doc/draft-ietf-wpack-use-cases/
    comment by rektide · 2021-12-03 · in We Need a Chromium Foundation
  40. …times. But never like this. This is truly apocalyptic destruction being wracked upon the web. [1] https://github.com/w3c/webextensions/pull/135/files#diff-ee4... [2] https://github.com/w3c/webextensions/issues/72 [3]…
  41. …developer? Here is a list of issues that extension developers have with requiring Service Workers: https://github.com/w3c/webextensions/labels/topic%3A%20servi... Just take a look at this work-in-progress MV3 version of a fairly popular…
  42. …for background scripts. Another simply puts background pages back, but behind a permission. [0] https://github.com/w3c/webextensions/labels/topic%3A%20servi...
  43. …with browser vendors and other extension developers. http://w3c.org/community/webextensions https://github.com/w3c/webextensions
    comment by dotproto · 2021-06-10 · in Introducing chrome.scripting
  44. …For the remaining 10%, I agree there is some risk - but per the webextension group's charter ( https://github.com/w3c/webextensions/blob/main/charter.md ) section on "Autonomy" > Given this, we expect browser vendors to offer APIs and…
  45. This is their charter: https://github.com/w3c/webextensions/blob/main/charter.md And the twitter announcement from the co-chair: https://twitter.com/xeenon/status/1400862543673921536 I'm cautiously optimistic that this will work well, but…
  46. ▲ 2
    WebExtensions Community Group Charter
    story by butz · 2021-06-05 · 0 comments