You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2022. It is now read-only.
As, the tile says, visit below website. And make sure inline-scripting is active. Host name is not displayed. Not sure, if its a bug or not..See the pic, lifehacker.com is not listed in the pane..
Hmm, it seems like this is consistent across all µBlock browser platforms.
Anyway, it seems (to me) like this is not a bug. Dynamic Filtering will show the various domains/hosts from which resources are being grabbed for the current tab. That doesn't include the page's host itself, because µBlock doesn't currently have a concept of blocking pages that are explicitly "navigated to" — I believe you can't block the mainframe page request.
In the default configuration, there are XHR requests that go out to When the scripts are disabled (as your screenshot shows), some XHR requests to lifehacker.com occur (and they're fine):
However, when scripts are blocked as your screenshot shows, the scripts that perform those XHR requests are blocked, so the XHR requests never occur. Since there don't appear to be any other resources in the page that are loaded from lifehacker.com, it doesn't show up in the Dynamic Filtering list.
As, the tile says, visit below website. And make sure inline-scripting is active. Host name is not displayed. Not sure, if its a bug or not..See the pic, lifehacker.com is not listed in the pane..
http://lifehacker.com/ublock-the-memory-friendly-ad-blocker-is-now-availabl-1681818949/all
Using v0.8.6.0-beta 6
Update 1: Same issue can be observed on Chrome (i have v0.8.5.7 )
The text was updated successfully, but these errors were encountered: