Skip to content

Loading…

host name not displayed in dynamic filtering frame, when inline-scripting is active.. #630

Closed
harshanvn opened this Issue · 3 comments

3 participants

@harshanvn

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

ublock lifehacker

Using v0.8.6.0-beta 6

Update 1: Same issue can be observed on Chrome (i have v0.8.5.7 )

@chrisaljoudi

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):

XHR

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.


@gorhill what do you think?

@gorhill

Definitely a bug.

This makes it impossible to override the more generic rules. Looking into this.

@gorhill

Right, it's yet another side effect of fix to #516.

@gorhill gorhill added a commit that closed this issue
@gorhill gorhill this fixes #630 357e226
@gorhill gorhill closed this in 357e226
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.