uBlock Origin / uBlock Origin Lite

[harlan4096]

uBlock Origin 1.48.0 released today on github, but probably takes a while until available on all app stores...

To install the stable build:

• Firefox: Review pending
  • uBO works best on Firefox.
    
• Chromium: Submission pending
  
• Edge: Install from Microsoft Store: Microsoft Edge Addons
  • The Microsoft Store version of uBO is published by Nicole Rolls
    
• Opera: Submission pending
  

New​

Readiness status at browser launch​

uBO's readiness at browser launch time is a particularly prickly issue on Chromium-based browsers,[1] especially more so since Chromium 110. This leads to numerous reports of "uBlock stopped working", which are simply caused by the fact that at launch time the browser started to load webpages before uBO was ready to filter properly (because the filter lists were not fully loaded in memory).

To reduce the number of reports caused by this issue which is outside of uBO's control, uBO's toolbar icon will now reflect its readiness status at browser launch.

1. A yellowish toolbar icon means that uBO is currently loading all filter lists into memory and as such is not ready to filter properly:
   
   
2. If additionally there is a yellowish ! badge while uBO is working toward readiness, this means network requests were fired by the browser which could not be processed by uBO, potentially leading to ads/trackers/etc. not being filtered in some of the already opened webpages:
   
   
3. Once uBO is ready to filter properly, a yellowish ! badge on a normally colored toolbar icon means that the current webpage was not filtered properly at browser launch, potentially causing the current webpage to be afflicted by ads/trackers/etc.:
   
   
4. To remediate the browser launch filtering issue on a given webpage, you can simply force a reload of that webpage, which as a result will bring back the badge to be rendered as expected:
   
   

For Chromium-based browsers, it is possible to automate step 4 above by checking the setting Suspend network activity until all filter lists are loaded in Filter lists pane in the dashboard. Caveat: in the past some users have reported this negatively interfered with page loading at browser launch time in some cases (example, example), hence why it is optional and not enabled by default in Chromium-based browsers.

With Firefox-based browsers, you should typically only see step 1 and 4 above, unless you disabled the setting Suspend network activity until all filter lists are loaded, which is enabled by default in Firefox.