Jump to content
CCleaner Community Forums
hazelnut

ublock users

Recommended Posts

ublock v1.9.2

 

gorhill released this

3 hours ago

 

Fixed:

Share this post


Link to post
Share on other sites

ublock v.1.9.6

 

gorhill released this

8 hours ago

 

Changes:

 

When uBO encounters the filter option other, it will internally add the filter option websocket to the filter. This is to keep compatibility with filter lists which are meant to be compatible with ABP, which categorizes websocket requests as other. Reference: #1943 (comment).

 

Fixed:

 

Firefox

Core

Share this post


Link to post
Share on other sites

ublock v1.9.8

 

gorhill released this

2 days ago

 

Changes

 

Core code related to static and cosmetic engines has been refactored to take advantage of ES6 Set/Map (related issue: #1070). Polyfilled versions of Set/Map are provided for compatibility with Chromium 37 and less[1], and for Pale Moon 26 and earlier[2]. While at it, I also revisited some of the inner-most loops executed at load time to remove other observed overheads in profiling results.

 

Benchmarks shows that there are good gains to be had in performance and memory efficiency when using ES6 Set/Map. The performance gains are especially true when dealing with collections with a lot of misses, which is typical of the static and cosmetic filtering engines ni uBO.

 

Following the above refactoring, profiling Chromium/Firefox, I observed:

  • Non-selfie case: uBO will roughly load in about half the time, because:
    • Using ES6 Set and Map instead of Object
    • No longer using String.split to split lines into fields = less memory allocations = less work for garbage collector
  • Selfie-case: there is a marginal performance improvement at most in boot time -- make sense since a selfie is just a no-parsing-at-all load mechanism regardless of how the data is represented internally.

Chromium + uBO with default settings + EasyList Germany -- forgot to un-check it before profiling...
2216d7ae-78db-11e6-8a8d-69bedb447dfc.png

 

Nightly + uBO with default settings
5d8b8100-7f38-11e6-9c34-e418b72cd165.png

 

Closed as fixed: Chromium

Core
  1. There is a "Enable Experimental JavaScript" flag which can be used to enable ES6 Set/Map for Chromium 31-37. When the polyfilled Set/Map are used for Chromium-based browsers, uBO's memory usage will be higher, as using Object as Set or Map is less efficient memory-wise (though still fast).
  2. For Pale Moon 26 and less, Set/Map iterators are not ES6-compatible.

Share this post


Link to post
Share on other sites

ublock v1.9.12

 

gorhill released this

2 days ago

 

Closed as fixed: Firefox

Share this post


Link to post
Share on other sites

ublock v1.9.16

 

gorhill released this

2 days ago

 

Changes:

 

Some work has been done on the element picker:

  • can now handle procedural cosmetic filters (:has, matches-css, :xpath), and also the special operator :style -- matching elements of such filters will be highlighted like normal CSS selector-based filters.
  • an invalid filter in the input field will now trigger a visual cue: the background of the input field will be reddish.
  • the number of elements on the current page matching the filter in the input field is now displayed in the bottom right corner of the input field.
  • the preview mode is now sticky, i.e. you can modify the filter in the input field without being kicked out of preview mode. Convenient when creating :style-based cosmetic filters.

The Privacy setting "Disable hyperlink auditing/beacon" has been changed to "Disable hyperlink auditing", and network requests of type beacon are no longer blanket-blocked. The network requests of type beacon will now be filtered just like any other network requests, according to the current filters/rules. [need to update wiki doc].

 

Network requests of type csp_report will be blocked regardless of filters/rules when there is a probability they are fired as a result of uBO internally redirecting one or more network requests to neutered resources. In such case, uBO considers these csp_report network requests as "spurious" and blocks them. An example of such spurious CSP reports being fired as a result of uBO redirecting resources is https://medium.com/ (see dev console when loading a page from that site), where a CSP report is fired by the browser as a result of uBO redirecting Google Analytics script to uBO's neutered version.

 

Closed as fixed:

 

Chromium

Core

Share this post


Link to post
Share on other sites

ublock v1.10.0

 

gorhill released this

21 hours ago

 

Changes Dynamic filtering pane

 

The dynamic filtering pane in the popup panel is now available in read-only mode to users who did not enable "I am an advanced user" in Settings:

9869bf24-a663-11e6-9189-02a470f95a96.png

 

The rationale for this change is explained in issue 2010. It still is collapsed by default, but can be brought up by clicking the "requests blocked" or "domains connected" fields in the main area.

 

Template-based scriptlets

In order to promote the reuse of injectable scriplets across different sites, it is now possible for a scriptlet to accept arguments. The arguments are comma-separated and appear after the token, for example (a real case):

golem.de##script:inject(abort-on-property-write.js, _sp_)

In the example above, the scriplet abort-on-property-write.js contains a placeholder for one argument, which placeholder will be replaced with the argument _sp_. Placeholders for scriplets which accept arguments will always be for string values (reminder that injectable scriplets are part of the project, never from an external party).

 

Advanced settings

A new "Advanced settings" pane, available only to advanced users. It contains settings which are experimental, or which are of interest to advanced users who want more control over how uBO behaves internally. I do not want to bloat the Settings pane in the dashboard with settings which are of interest only to a minority of users or which are experimental: this is where the new "Advanced settings" pane is useful.

When you enabled "Advanced users" in the Settings pane, a cogs icon will appear next to that setting. Click this cogs icon to access those "hidden" advanced settings:

2800dcd4-a44e-11e6-9bc8-a5e0c960262c.png

 

The UI of the advanced settings page is purposefully stern. Keep in mind that whatever settings you see in there may be experimental and could be removed at any time in the future.

 

Experimental advanced setting of interest: suspendTabsUntilReady (default to false), to prevent uBO from establishing any remote connection at launch before all filter lists/settings have been fully loaded (related issue #1327). How well it works will have to be evaluated by users.

 

WebExtensions

From now on, there will be a Firefox's WebExtension version of uBO (see uBlock0.webext.zip below, see "Temporary Installation in Firefox" on how to install on Firefox). Do not bother trying it out if you do not have Nightly 52.0a1 (2016-10-29) or later installed. Also, do not open issues here for the WebExtension version of uBO -- it is still at an experimental stage and there are things which are known to be missing in the API for uBO to fully function: see bugzilla 13099260.

 

Closed as fixed: Firefox:

Core

Share this post


Link to post
Share on other sites

nothing to thank, gladly done :)

 

ublock v1.10.2

 

gorhill released this

7 hours ago

 

 

Changes

 

Cosmetic filtering

 

Implementation of cosmetic filter operator :matches-css has been revised according to the discussion at #1930 (comment) and request in uBlockOrigin/uAssets#212:

  • :matches-css now accept no more than one single style property. If more than one style property must be matched on the same node, you will need to chain them (i.e. div##matches-css(...):matches-css(...) -- ability to chain is coming for next release). Since there is only one style property, do not use trailing ;.
  • :matches-css-before() and :matches-css-after() are now also available to specifically match style property for the pseudo elements :before and :after on a node.
  • Support the use of regexes for property matching: if the first and last character of the value to match is /, the value will be deemed to be a literal regular expression which must be matched.

Dashboard

 

The last dashboard's pane you visited will be automatically opened next time you open the dashboard (issue #2206).

____________________________________________________________________

 

Closed as fixed:

 

EdgeFirefoxCore

Share this post


Link to post
Share on other sites

ublock v1.11.0

 

gorhill released this

3 days ago

 

Changes

 

Asset managements was refactored: details.

 

The user interface of the "3rd-party filters" pane has been revisited:

  • To render better in devices with smaller screen.
  • Clicking "Update now" is no longer a blocking operation.
  • The home icon is a link to the support site for a given filter list.
  • The clock icon replaces the "purge cache" label.
    • Click to mark a filter list as out-of-date.
  • The custom filter lists input field has been repurposed to import external filter lists, as opposed to declare external filter lists as was the case before.
    • An imported filter list will have an X icon aside its name, to be used to remove the custom filter list.
  • You can now hide unused filter lists by clicking the global filter count at the top.

Procedural cosmetic filters can now be chained and recursive (something which was planned) .

 

New procedural cosmetic filter operators:

  • :has-text(argument): to filter elements according to whether they have a specific text string found in them. Use /.../ to match a literal regular expression instead of plain text.
  • :if()/:if-not(argument): use to implement recursion, argument is itself a valid procedural cosmetic filter, but can also be a plain CSS selector.

The cost of parsing procedural cosmetic filters has been moved from content script-time to filter list compile-time, i.e. done only once when a filter list is updated.

 

Documentation about procedural cosmetic filters has been updated.

 

The element picker supports all procedural cosmetic filters, i.e. it will also provide visual feedback as you enter manually such filters in the input field. Invalid filters, procedural or not, will be labelled with a bright red E.

 

Closed as fixed Firefox

Firefox for AndroidCore

Share this post


Link to post
Share on other sites

ublock v1.11.2

 

gorhill released this

4 days ago

 

Changes

Better support for selecting broad cosmetic filters (Ctrl-click) in element picker (1c4347d).

Closed as fixed: EdgeFirefoxCore

Share this post


Link to post
Share on other sites

It's odd that uBlock never automatically updates the filter list subscriptions on my WinXP system. However on my mother's Win10 laptop it always automatically updates.

Share this post


Link to post
Share on other sites

"uBlock Origin" was recommended to me on another forum and I installed it a few days ago in my Chrome browser.  Seems really good.

Share this post


Link to post
Share on other sites

agreed Razz, it seems one of the few ad-blockers out there that have resisted the trend in allowing 'paid for' ads through their filters.

Share this post


Link to post
Share on other sites

ublock v1.12.0

 

gorhill released this

4 days ago

 

Changes

 

New static network filter option: badfilter. Using this option will prevent another filter to be loaded in memory. See uBlockOrigin/uAssets#192 for rationale for having such a filter option.

 

Chromium/Firefox WebExtension

 

Ability to support more request types from webRequest API: csp-report, font, media, websocket, and actually whatever is part of webRequest.ResourceType. This means uBO will be able to natively filter websocket connection attempts starting with Chromium 58.

 

Firefox

 

The webext version for Firefox has been converted into a hybrid version, to allow seamless migration of uBO's settings/data from a legacy extension to webext extension. I consider this webext version of uBO to be fit to release to AMO if the current stable Firefox version (52) supported all the proper WebExtensions API required by uBO. All the blocking issues have been resolved, but the fixes will be available in a future stable version of Firefox.

 

Update: due to auto-update snafu, the webext version of uBO has been given a different id than the official one, this will guarantee that auto-update won't cause issue (you will have to update manually if using the webext version).

 

Important: If you install the webext version of uBO (you need the most recent build of Nightly), this is what will happen:

 

When you launch uBO/webext for the first time, it will read all your settings/data from the old storage and migrate them to the new webext storage. This happens only if uBO/webext can find a file named ublock0.sqlite. This will happens only once, the first time you install uBO/webext. Depending of how much data there is to migrate, this may cause your browser to work hard during that first launch and delay readiness.

 

Once the data from the uBO/legacy has been migrated to uBO/webext, each version of uBO will only see its own data, meaning no change in settings in one version will be seen by the other version. If you remove uBO/webext, this also removes the storage associated to it, meaning re-installing uBO/webext following removal will cause the storage migration code to kick in again.

 

Closed as fixed:

 

Chromium

EdgeFirefoxFirefox/WebextensionCore

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×