Skip to content

Loading…

inline scripts no being properly blocked (in firefox) #733

Closed
louiz opened this Issue · 5 comments

2 participants

@louiz

In firefox 35.0.1, with uBlock 0.8.7.0, blocking inline scripts does not seem to work for me.

For example on this page http://www.smbc-comics.com/index.php press the key “x”, and this will load a random comic. This feature is done using the inline javascript that start line 35 of HTML.
I’m using these settings: custom filters
With those, I would think that this script would be blocked and these keyboard features would be disabled, but in fact it doesn’t.

@gorhill

Works as expected: the inline script tags are blocked when the page is loaded. If you toggle inline script tags, the page needs to reload for the rule to take effect.

@gorhill gorhill closed this
@louiz

It doesn’t work as expected with me.

The scripts are not blocked when I join suck a page for the first time (even if the inline scripts are already blocked for this site, in the dynamic filters, as shown in my previous screenshot, before I open that page).

But then, on the next page reload (without changing any filter), they are correctly blocked.

I simply reproduce like that:

@louiz

Oh, I think I have something important: apparently scripts are not blocked if the page is loaded in a new tab. If you however open a tab, load google.fr in it, then enter http://www.smbc-comics.com/index.php?db=comics&id=3650 in the address bar, hit enter, then the scripts are correctly blocked in that page.

@gorhill

Yes, looks like #531.

@louiz

Ok, if it’s already known, I’ll just wait for a fix of #531, thank you.

@andre-hub andre-hub pushed a commit to andre-hub/uBlock that referenced this issue
@gorhill gorhill this fixes #733: filter appears to be obsolete d766c05
@andre-hub andre-hub pushed a commit to andre-hub/uBlock that referenced this issue
@gorhill gorhill #733: reverting last commit, filter is not obsolete after all 0fbbaed
@andre-hub andre-hub pushed a commit to andre-hub/uBlock that referenced this issue
@gorhill gorhill this fixes #733 fa8eb71
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.