uBlock Origin 1.17.5b10

Changes

Changes to the logger in order to address issues raised in #3654:

• show the hostname of the document which caused the resource to be fetched
• show the 3rd-partyness of a resource relative to both the page and the document fetching the resource
• new visual hint to denote tab-less network requests
• a popup panel button linked to the tab selector

Examples:

The 4th column shows the hostname of the document which caused the resource to be fetched. The document hostname

is what is used when evaluating the 3rd-partyness in static filters.

The 5th column shows the "3rd-partiness" of the resource. 1 means 1st-party, 3 means 3rd-party. As seen in

the screenshot above, there can be one or two numbers to convey partyness:

• 1: the resource is 1st-party to the current page
• 3: the resource is 3rd-party to the current page
• 3,1: the resource is 3rd-party to the current page, but is 1st-party to the embedded frame from within which it is fetched
• 3,3: the resource is 3rd-party to the current page, and 3rd-party to the embedded frame from within which it is fetched
• 1,3: the resource is 1st-party to the current page, and 3rd-party to the embedded frame from within which it is fetched (should be a quite rare occurrence if any)

Hovering the mouse over the partyness cell will show the domain names involved in a tooltip.

As can be seen in the screenshot above, it contains all (realistic) cases, hence why I picked the site as example.

You may use logger filter expression to filter according to partyness. For example, use |3 to see only 3rd-

party network requests. Use |3, to see only network requests made from within embedded 3rd-party frames.

The visual representation of behind-the-scene network requests has changed, as seen in the following

screenshot:

Since the fix to enable the filtering of behind-the-scene network requests in 1.15.20, a distinction has existed

between tabless network request with a known origin and tabless network requests with an unknown origin.

The latter should by now be quite rare, while the former are now filtered by uBO just as with other network

requests. So as seen in the screenshot above, there are many tabless network requests, but with a known

origin (the site uses a service worker).

The 2nd column in the logger used to convey whether a network request was behind-the-scene or not, and

this column has now been removed. This column was also used to bring up the popup panel, and this did not

make much sense really, since an entry in the logger could be obsolete and the shown popup panel would be

completely unrelated to it. Hence now the popup panel is brought up with the uBO icon at the top, and the

content of the popup panel will always match whatever tab is currently selected in the logger.

Closed as fixed:

Chromium

• Use IndexedDB as cache storage on Chromium platform

Core

• uBO does not unhide nodes no longer matching procedural cosmetic filters
• Static extended filtering: fix empty hostnames not being detected/handled
• Cosmetic filter "##" or "##tag," same as "##*" in element picker only
• !#include directive should insert sub-content at directive point
• 3rd-gen HNTrie
• Duplicate specific cosmetic filters not discarded when "Ignore generic" is enabled
• $generichide is still applied even when website is whitelisted
• Change "IDN: ABPindo" to "IDN, MYS: ABPindo"
• Changing the button for the NOR list
• Filter list view - ugly/messy line breaking/wrapping at minus sign char
• Remember and reuse last position/size of the logger popup window
• Logger filter lookup overlay should scroll when filter too long
• Improve representation of behind-the-scene network requests in the logger