-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Firefox WebExtensions
This page may update often until there is a stable release of uBO/webext.
Tentative schedule | July 19 | Aug. 10 | Aug. 22 | Sep. 19 | Nov. 14 |
---|---|---|---|---|---|
Firefox stable is... | Firefox 54 | Firefox 55 | Firefox 57 | ||
AMO dev channel | uBO/webext hybrid |
uBO/webext | |||
AMO stable channel | uBO/webext hybrid |
uBO/webext | |||
Blocking | |||||
Non-blocking |
1313401 1303384 |
- uBO/legacy: compatible with Firefox 24 to Firefox 56
-
uBO/webext-hybrid: compatible with Firefox 54 to Firefox 56
- Use to migrate settings from uBO/legacy to uBO/webext
- uBO/webext: compatible with Firefox 54 and above
The first time uBO/webext-hybrid executes, there might be a noticeable delay[1]: this is caused by the fact that uBO/webext-hybrid will import all the data from legacy storage, into webext storage. This is done only the first time the uBO/webext-hybrid is executed, after this the import step will be skipped.
If you subsequently remove uBO/webext-hybrid, this will cause the webext storage to be removed by Firefox, and upon re-installing the uBO/webext-hybrid version, the import code will again kick in.
Note that uBO/webext-hybrid will still be labelled as "Legacy" in about:addons
, because uBO/webext-hybrid is really an embedded WebExtension. Once the legacy storage has been imported at first install by the thin legacy wrapper, uBO/webext-hybrid will fully function as a pure webext extension despite the "Legacy" label.
The legacy storage is left untouched by uBO/webext-hybrid, so you can always go back to uBO/legacy (stable release) if you do not want to use the webext-hybrid version in the short term.
[1] A few seconds on my older than mainstream CPU with default settings/lists. The more filter lists you have enabled, the longer it will take.
As per documentation, only with Firefox Mobile 55 (beta) you can access uBO's popup panel.
However it appears there is an issue with installing webext extensions on Firefox for Android 55, the browser thinks the extensions are corrupted -- this does not appear specific to uBO/webext. Consequently, for now it seems it's best to stick to uBO/legacy on Firefox for Android. Update: this is fixed: https://bugzilla.mozilla.org/show_bug.cgi?id=1367494.
-
script:contains
filters will stop working- uBO's own filter lists have long ceased to rely on this filter syntax to solve reported filtering issues.
-
cosmetic filters will no longer use the browser's user stylesFixed with f32868766340e2fb8ec689f4b5683a413de847b6 - uBO/webext has limited access to behind-the-scene network requests, unlike uBO/legacy which had full access to all behind-the-scene network requests. For example, you won't be able to see (and block) network requests made by other extensions. Related: "Support moz-extension: urls in MatchPattern".
As stated above, the current version of uBO/webext-hybrid is really an embedded WebExtension. The pure webext version of uBO, uBO/webext is now available in the Releases section, and in the dev channel on AMO.
Stable release of uBO/webext must be available to all users when Firefox 57 is released.
However, before releasing uBO/webext to stable channel on AMO, I must release uBO/webext-hybrid first, a necessary step for a seamless transition to uBO/webext.
These are the dates of coming Firefox stable release versions, as per RapidRelease/Calendar:
- Firefox 55: August 8
- Firefox 56: September 26
- Firefox 57: November 14
This is what I plan:
- August 8 + 2 weeks
- uBO/webext-hybrid published on AMO's stable channel
- uBO/webext published on AMO's dev channel
- uBO/webext-hybrid publication + 4 weeks = September 26
- uBO/webext published on AMO's stable channel
- Could be sooner if uBO/webext-hybrid is being used by most users sooner than expected.
For all those Firefox and Firefox-based browsers based on Firefox v53 and less, the dev channel of uBO will cease to work, and they will have to install manually the xpi
version from the repo here if you want to keep using the dev version of uBO, or install the stable version of uBO on AMO.
As of writing, there is no plan to cease development of uBO/legacy. Hypothetically, this may change in some future if ever it becomes really non-trivial to keep a working the legacy version.
I do expect users of legacy versions of Firefox to test and report any issues with uBO -- I can't afford the time needed to test all those versions.
Issue #2795 will be a collection of bugzilla.mozilla.org issues which currently affect the uBO/webext specifically.
Be sure to create backups of your uBO settings, if the transition from uBO/legacy to uBO/webext fails, you can always just restore all your settings from the backup file (see Settings pane in the dashboard for the backup/restore features).
uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean.
- Wiki home
- About the Wiki documentation
- Permissions
- Privacy policy
- Info:
- The toolbar icon
- The popup user interface
- The context menu
-
Dashboard
- Settings pane
- Filter lists pane
- My filters pane
- My rules pane
- Trusted sites pane
- Keyboard shortcuts
- The logger
- Element picker
- Element zapper
-
Blocking mode
- Very easy mode
- Easy mode (default)
- Medium mode (optimal for advanced users)
- Hard mode
- Nightmare mode
- Strict blocking
- Few words about re-design of uBO's user interface
- Reference answers to various topics seen in the wild
- Overview of uBlock's network filtering engine
- uBlock's blocking and protection effectiveness:
- uBlock's resource usage and efficiency:
- Memory footprint: what happens inside uBlock after installation
- uBlock vs. ABP: efficiency compared
- Counterpoint: Who cares about efficiency, I have 8 GB RAM and|or a quad core CPU
- Debunking "uBlock Origin is less efficient than Adguard" claims
- Myth: uBlock consumes over 80MB
- Myth: uBlock is just slightly less resource intensive than Adblock Plus
- Myth: uBlock consumes several or several dozen GB of RAM
- Various videos showing side by side comparison of the load speed of complex sites
- Own memory usage: benchmarks over time
- Contributed memory usage: benchmarks over time
- Can uBO crash a browser?
- Tools, tests
- Deploying uBlock Origin
- Proposal for integration/unit testing
- uBlock Origin Core (Node.js):
- Troubleshooting:
- Good external guides:
- Scientific papers