-
Notifications
You must be signed in to change notification settings - Fork 77
Firefox WebExtensions
Stable release of uBO/webext has been available on AMO since early September 2017. uBO/webext is compatible with Firefox 52 and above. With Firefox 52 specifically, some features in uBO/webext may be disabled.
uBO/webext works best with Firefox 57 and above, and with multi-process enabled.
There are many reports of people experiencing issues with some websites, or images not loading, etc. Turns out many of these are a result of using some legacy extensions along uBO/webext. For instance, Reek's AAK in GreaseMonkey has been causing issues with images not loading.
If you experience such issue, you will have to disable all your legacy extensions and see if this fixes your issue. If so, then you will have to re-enable your legacy extensions one by one to find the one(s) causing the problem.
Those legacy extensions can cause multi-process to be disabled in your browser, and apparently when multi-process is disabled, this can cause many cases of page load failure.
Update (2018-06-30): if you experience above problems in Waterfox then this problem will probably be fixed in next Waterfox release (56.2.2-56.3?)
Everything is moving to WebExtensions, so it might be just a good time to start giving up on legacy extensions, they are not going to be supported at all in a couple of weeks when Firefox 57 is released. See if there is a beta webext version of any of your legacy extensions. For example, there is a beta webext version of Greasemonkey on AMO. [via archive.org]
There are also Firefox issues specific to webext extensions which can cause a web page to load improperly:
-
Extension with listener at webRequest.onHeadersReceived breaks navigation (crash/blank page) when the previous page performs sync XHR upon unload
- duplicate of 1396395 - Firefox crashes when submitting form - RESOLVED FIXED in Firefox 58
-
Empty page using uBo / ABP webext (even whitelisting the site)
- duplicate of 1379148 - document.write does not synchronously modify a document if an extension has content scripts at document_start - VERIFIED FIXED in Firefox 57, supposedly fixed in Waterfox 2019.10 (rel1, rel2, rel3, merge)
- Presence of an Webextension makes the head element missing on (iframe) load
Another option is to install uBO 1.13.8 and disable auto-update for it.
Having issues with uBO's cache storage being wiped-out on every restart of the browser? See if https://forums.mozillazine.org/viewtopic.php?f=9&t=3034189 helps.
Update (2018-06-30): if you still have problems with filter list being out of date on every restart check this Mozilla bug 944918 - indexedDB broken - UnknownError - Error opening Database In overall your IndexedDB database may be corrupted (in various ways) and only way to fix this is to find database folder and remove it. One special case of "corruption" may appear when you browse database folders and you file explorer drops hidden files in database directory (for example .directory
dropped by Dolphin in KDE) - deleting these unwanted files will fix the problem.
Firefox for Android 56: you can access the popup panel using the "uBlock Origin" menu entry. However, the dashboard can't be accessed through about:addons
. This is fixed in Firefox for Android 57. The workaround is to open uBO's dashboard through uBO's popup panel. Once you access the dashboard, you could create a bookmark out of it to allow direct access in the future.
Firefox for Android 55: As per documentation, only with Firefox Mobile 55 (beta) you can access uBO's popup panel.
-
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".
For all those Firefox and Firefox-based browsers based on Firefox v52 and less, uBO from https://addons.mozilla.org/firefox/ 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.
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 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.
If you still want to use uBO/legacy, a volunteer created an extension to enable uBO/webext to update automatically: https://github.com/JustOff/ublock0-updater.
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).
[1]: 2018-06-30 updates and solution for "corrupted database" problem thanks to grahamperrin message
- 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