ublock users

[trium]

firefox legacy v1.16.4.1

 

gorhill released this

5 days ago

 

no entrys... for fixed

[trium]

ublock v1.16.10

 

gorhill released this

a day ago

 

Closed as fixed:

Chromium

• Early injection of scriptlets (see c5d8588).
  • Using tabs.executeScript() to inject scriptlets at document_start allows to inject scriptlets earlier and hence increase likelihood that the scriptlets will win the race against a page's scripts.

Firefox

• HTML filters occasionally lost effectiveness

Core

• Round hour up to nearest day

[trium]

ublock v1.16.12

 

gorhill released this

5 days ago

 

Closed as fixed:

Chromium-based browsers

• Fixed incorrectly rendered overview pane of popup panel -- as seen in this screenshot from this Reddit post.

Core

• CSS pseudo element: -webkit-scrollbar
• badfilter + matching duplicate user filter created from picker or logger may rarely cause a js exception

[trium]

firefox legacy v1.16.4.2

 

gorhill released this

on 17 Jun

 

• uBO tooltips conflicts with browser tooltips (fixed by @janekptacijarabaci)
• Commit history since 1.16.4.1

[trium]

firefox legacy v1.16.4.3

 

gorhill released this

3 days ago

 

Closed as fixed:

• Race condition at filter lists load time potentially breaking highly-generic cosmetic filters (dcd98f4)
• Inifinite update attempts with "AdGuard Experimental filter"
• Commit history since 1.16.4.2

[trium]

ublock v1.16.14

 

gorhill released this

3 days ago

 

Closed as fixed:

• Race condition at filter lists load time potentially breaking highly-generic cosmetic filters (dcd98f4)
• Cursor jumps to next matched item when adding char to search
• Inifinite update attempts with "AdGuard Experimental filter"
• Odd sorting in popup domains list when domains have same SLD but different TLD
• Cosmetic rules not logged for embedded YouTube videos

[trium]

firefox legacy v1.16.4.4

 

gorhill released this

2 days ago

 

• Trivial fixes for Thunderbird compatibility.
• Commit history since 1.16.4.3

[login123]

Thanks, Trium.

[trium]

[trium]

ublock v1.16.16

 

gorhill released this

9 hours ago

 

New

A new pane has been added in the dashboard for the Firefox version of uBO: Shortcuts. The purpose is to be able to assign keyboard shortcuts to some common operations. (Chromium-based browsers have a centralized keyboard shortcut UI, so the pane is not necessary for Chromium-based browsers.)

Closed as fixed:

Firefox

• Settings cannot be reset on Beta and Nightly Firefox
• Add a pane in the dashboard (Firefox only) to assign keyboard shortcuts
  • The new pane will be available for Firefox 60+ only.

Core

• Element picker cannot be toggled before a site is fully loaded
• Logger: generic hiding rule recorded as active when $generichide in effect
• Filter for dynamically added class is not logged
• Logger: Popup which shows the used filter is empty

[trium]

ublock v1.16.18

 

gorhill released this

2 days ago

 

I decided to create an emergency fix for a bug which was spotted for uMatrix but which also affects uBO:
"My rules tab hangs with cloud storage support"

If using cloud storage, there is a small probability uBO could be stuck in an infinite loop when reading back the data from the cloud storage, something which may occurs when the following conditions are fulfilled:

• You checked the setting "Enable cloud storage support";
• You saved data into the cloud storage for a given pane;
• The amount (in bytes) of data that was saved into the cloud storage for that given pane is rather high and such that the "chunkification" of that data results in a chunk count which is a multiple of 16;
  • Large amount of data is more likely for the "My filters" and "My rules" panes.
  • Sorry for the cryptic explanation, I don't know how else to describe this.
• You open the pane in the dashboard for which the conditions above are true.

If the bug is triggered, uBO could be stuck in an infinite loop in its main process, thus preventing it from doing its job.

This is not a regression, but rather a bug that has been hiding in there since quite a long time.

Commit history since 1.16.16

[trium]

ublock v1.16.20

 

gorhill released this

2 days ago

 

No change from 1.16.18, I didn't upload properly on AMO and I was not allowed to re-upload without bumping up the version number.

[trium]

ublock v1.17.0

 

gorhill released this

a day ago

 

New

Per-site JavaScript master switch

A new per-site switch has been added to the popup panel, which acts as a master switch for JavaScript for the current site.

This master switch has precedence over dynamic filtering rules and static filters related to script resources.

Furthermore, when JavaScript is disabled through this master switch, noscript tags will be honoured on a page (as opposed to when just using filters/rules to block script resources).

As with some other per-site switches, the default state of per-site JavaScript master switch can be set in the Settings pane, thus allowing to disable JavaScript everywhere by default, and enable on a per-site basis:

JavaScript master switch rules appear as no-scripting: [hostname] true entries in the My rules pane.

Temporarily toggle per-site switches

From now on, changes to the state of per-site switches will be deemed temporary if and only if the overview panel is visible, regardless of whether "advanced user" mode is enabled.

When the overview panel is not visible, toggling a per-site switch will cause the change to be permanent (i.e. same behavior as before).

However, when the overview panel is visible, toggling a per-site switch will cause the change to be temporary. In such case, there will be an eraser and a padlock icon in the overview pane, which can be used to revert or persist the current state of all the per-site switches.

Cache storage compression

A new advanced setting: cacheStorageCompression, default to true. When true, uBO will lz4-compress data before storing it in its cache storage in supported platforms. Currently, the only supported platform is Firefox/Firefox for Android.

The cache storage is used for storing downloaded filter lists, compiled filter lists, selfies. See uBlockOrigin/uBlock-issues#141 for related discussion.

Closed as fixed

Firefox

• Error loading from the disk cache pages obtained by blocking remote fonts
• "Storage used" in settings tab says "? bytes"
  • It's really a workaround, consider the reported figure to be an on-the-low-side estimate
• Element picker mode in Firefox CSS failure on denuvo.com

Firefox for Android

• Cannot open Logger. Element picker/zapper does not switch tabs.

Core

• Use +js name for logging
• No reverse-lookup for logged HTML filter
• EasyList Thailand added to stock filter lists
• Various spelling fixes
• “manualUpdateAssetFetchPeriod” setting doesn't save the changes
• False positive detection of popups is broken
• "uBlock — Assets" should be changed to "uBlock₀ — Assets" in its tab
• Minor JS errors in dashboard
• Code exception in contentscript.js (vAPI.setTimeout) when opening Chrome last session tabs that are partly cached
• Element picker mishandles identifiers with backslashes
• Minor usability issue: block all scripts
• Toggle option changes are always permanent
• uBlock Origin doesn’t honor noscript tags when blocking JS

[Andavari]

The new version in the post above also removes the ability to be used on old versions of Chrome/Chromium used on older OS legacy machines with XP/Vista. Can't remember exactly since I'm not on the old computer but I thought it stated Chrome/Chromium v51 or v52 is required.

[trium]

firefox legacy v1.16.4.5

 

gorhill released this

6 days ago

 

Closed as fixed:

• I cannot subscribe to filter lists, with ublock origin legacy 1.16.4.4 (fixed by @gwarser)

[trium]

ublock v1.17.2

 

gorhill released this

4 days ago

 

No change since 1.17.0: this release is for the benefit of Firefox users, who will be able to take advantage of an up to date resources.txt asset. This new version will be published on AMO only.

[trium]

ublock v1.17.4

 

gorhill released this

Dec 1, 2018

 

Notes

I will keep bringing in WebAssembly ("wasm") versions of key portions of code where it is found to be beneficial. In this release, a wasm version of the algorithm used to lookup a hostname from a set of hostnames has been created (related benchmark page).

However, only the Firefox version of uBO benefits from this at this point, as it's is not possible to use wasm in the Chromium version without adding 'unsafe-eval' to the extension's own Content Security Policy in its manifest -- which is not something I am willing to do (my view is that any extension using 'unsafe-eval' should be assumed malicious by default). It works in Firefox because the wasm module is loaded using a same-origin fetch, meaning the module can only be loaded from uBO's own package, which is probably what Chromium ought to implement.

Closed as fixed

Firefox

• When pasting multiple lines into the rules editor they are joined together in a single line
  • Fixed by importing latest release of CodeMirror.

Core

• ##.ad.super from EasyList is causing ##.ad to not be applied
• Fix missing trailing asterisk in filter representation in the logger
• No context menu entry for data:* iframes (banners)
• UI Search field and it's search counter interfere with each other / unreadable
• "Update now" button flashes for 1 second before changing the count numbers
• Improve usability of temporarily disabling strict-blocking
• HTML filter exception doesn't work
• $badfilter does not work on a CSP filter

 

[trium]

 

Quote

 

Please note that GitHub no longer supports old versions of Firefox.

We recommend upgrading to the latest Safari, Google Chrome, or Firefox.

 

 

 

 

 

Quote

 

Supported browsers

 

We design GitHub to support the latest web browsers. We support the current versions of Chrome, Firefox, Safari, and Microsoft Edge.

Firefox Extended Support Release

We do our best to support Firefox's latest Extended Support Release (ESR). Older versions of Firefox may disable some features on GitHub and require the latest version of Firefox.

Beta and developer builds

You may encounter unexpected bugs in beta and developer builds of our supported browsers. If you encounter a bug on GitHub in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer.

 

 

[login123]

Thank you, Trium.   

[trium]

i wonder, why i become no updates of ublock

On 1.12.2018 at 20:31, trium said:

Firefox Extended Support Release

We do our best to support Firefox's latest Extended Support Release (ESR). Older versions of Firefox may disable some features on GitHub and require the latest version of Firefox.

i use ff esr 52.9.0 and ---> as a matter of fact - no new updates... but there are some

 

firefox legacy v1.16.4.6

 

gorhill released this

Dec 4, 2018

 

Closed as fixed:

• ##.ad.super from EasyList is causing ##.ad to not be applied

 

 

[trium]

firefox legacy v1.16.4.7

 

gorhill released this

Jan 20, 2019

 

Closed as fixed:

• Some rules doesn't show up in the Legacy version's logger

[Andavari]

I haven't and won't bother with those newer legacy versions for old versions of Firefox, I still have uBO 1.13.8 which works great on my WinXP system. Although I have the newest uBO on my Win10 system.

[hazelnut]

Might be an idea for Chrome and FF users to have a read of this thread about the proposed changes browsers are making regarding web requests by third party software.

https://github.com/uBlockOrigin/uBlock-issues/issues/338

It prompted Gorhill (uBlock Origin dev) to say this yesterday

Quote

I won't tell people what to do. I am pointing out that removing the blocking ability of the webRequest API means the death of uBO, I won't work to make uBO less than what it is now.

 

[Andavari]

There's always the HOSTS file, but it alone isn't 100% effective.

[hazelnut]

This issue and its consequences  is now being picked up by different news sites around the web

https://www.ghacks.net/2019/01/22/chrome-extension-manifest-v3-could-end-ublock-origin-for-chrome/

Could this have been Google's plan all along? Create a web browser and use it to combat the use of content blockers? Block some annoying ads, allow basic content blockers, and block any other form of content blocking to make sure that Google's advertising business improves again?

Some users would certainly move to Firefox if uBlock Origin, uMatrix, and other content blockers would no longer work in Chrome-based browsers. Even if millions would migrate, it would still leave Chrome dominate the entire desktop browser market.