µBlock Origin thread

gorhill · Post by **gorhill** » Tue Feb 16, 2016 12:59 pm

lakrsrool wrote:Problem solved. All I needed to do is update to current uBlock 1.6.1

Nothing in 1.6.1 would explain this. Have you tried forcing an update of your filter lists prior to install 1.6.1?

lakrsrool · Post by **lakrsrool** » Wed Feb 17, 2016 6:54 am

No I hadn't tried any Filter List updates prior to updating the add-on version to 1.6.1 from version 1.5.5. I should have thought of doing that, so probably this is why the problem got resolved. :idea:

As an afterthought, could it have been a combination of the uBlock version and the Pale Moon browser?

I ask this because I do not have this problem with Chrome using an older 1.5.6 version of uBlock and since I rarely use Chrome I haven't done any Filter List updates for probably at least 6+ months (far longer than PM) in the Chrome browser. So using the same 7 Filter lists as in Pale Moon but all much older than in Pale Moon (needing updates and some even "out of date") didn't cause a problem like this in that browser.

Post by **barbaz** » Fri Apr 01, 2016 1:37 pm

How to search through all 3rd-party filters within uBlock Origin? I mean, in this type way.

Post by **barbaz** » Mon May 16, 2016 4:10 pm

When a element is hidden by uBlock Origin, how to tell which hiding rule(s) AKA cosmetic filters are hiding it? The logger seems to only show some applied hiding rules, not all. In the devtools Inspector it just shows a massive list of all the globally-applied hiding rules

gorhill · Post by **gorhill** » Tue May 17, 2016 2:08 pm

barbaz wrote:When a element is hidden by uBlock Origin, how to tell which hiding rule(s) AKA cosmetic filters are hiding it?

Try uBO's inspector tool. It's the "</>" button at the top of the logger page.

Post by **barbaz** » Tue May 17, 2016 4:24 pm

Thanks but unfortunately the page in question is a local .maff archive (file:///home/.../xxx.maff), the <body> element is what's hidden and the logger's inspector is blank

(It does work for me on http(s) pages though

. I'll see about getting a issue filed on github tracker.)

Anyway, I've discovered that actually the devtools shows non-applicable part(s) of a comma-separated CSS selector as light gray and the applicable part(s) in color, and also that devtools didn't show me the entire class list of the <body> - it was hiding from me the portion that would be obviously susceptible to my hiding filters :roll:

This is what's shown:

Code: Select all

<body style="display: none ! important;" class="lifehacker custom-skin permalink en-US f_advancedtiming_off _spentincomments_on f_timing_on f_unishare_off f_userstats_on" data-timezone-offset="-25200000">

This is what it really is:

Code: Select all

<body style="display: none ! important;" class="lifehacker custom-skin permalink en-US f_advancedtiming_off f_amazon_on f_asset_636x90_off f_asset_970x90_off f_bannerheader_off f_bannerheader2_off f_bannerheadlines_off f_childrenbyactivity_off f_cleanwaterfall_off f_develop_off f_editoralpha_on f_editorengine_default f_feed_off f_fixsidebarad_on f_fullwidthreplies_off f_fullwidthrepliesswitch_off f_gpt_on f_hybridtoolbar_on f_jsdebug_off f_largethumb_left_off f_largethumb_right_off f_maintenance_off f_manageblog_off f_moatads_promoted_off f_mobilefirst_off f_packages_on f_panno_on f_postng_on f_promoteddisplay_default f_recommendbylikes_on f_recommended300_on f_recommendedsidebar_off f_relatedmodule_off f_repliesbyactivity_off f_replyprompt_off f_replywithshare_off f_show_custom_bylined_off f_sidebar_top_uses_subdomain_off f_sidebarscroll_on f_sitedropdown_on f_slimtoolbar_on f_social_off f_superuser_off f_textannotation_on f_timespentincomments_on f_timing_on f_unishare_off f_userstats_on" data-timezone-offset="-25200000">

Hopefully I can turn off that "feature"...

Post by **barbaz** » Tue May 17, 2016 8:53 pm

barbaz wrote:Hopefully I can turn off that "feature"...

about:config > set devtools.markup.collapseAttributeLength to -1
Enjoy seeing all! Awesome!!!!!!!!!!!!!!!!

Post by **barbaz** » Fri May 20, 2016 7:01 pm

Anyway, back to the logger's inspector being blank, I noticed that issue also occurs with arstechnica, and I think it is because currently some resource there isn't finishing loading. I would suspect a similar root cause with the .maff files, especially since the uBlock Origin inspector works fine with a normal local HTML file.

Will need to figure out how to cause a resource (I'm thinking an image) to hang loading on my local server in order to confirm for sure that this is the case. If anyone knows how to do this please let me know

(My server runs nginx and I have root access.)
EDIT Jeez, searching really unhelpful and just gets THIS of all things https://www.youtube.com/watch?v=oHg5SJYRHA0 :roll:

Seriously https://duckduckgo.com/?q=how+to+make+a+resource+hang+loading+on+the+server+side&kak=-1&kd=1&ia=videos&iai=oHg5SJYRHA0

gorhill · Post by **gorhill** » Sat May 21, 2016 2:25 pm

barbaz wrote:Anyway, back to the logger's inspector being blank, I noticed that issue also occurs with arstechnica, and I think it is because currently some resource there isn't finishing loading.

Thanks for investigating, it does appear this could be the cause, the injected script to analyse/report the DOM does not kick in until the `load` event is triggered. Could you open a formal issue for this? At first glance it looks like this can be fixed without too much complications.

Post by **barbaz** » Sat May 21, 2016 3:15 pm

gorhill wrote:Could you open a formal issue for this?

Sure, I'll see to that a formal issue gets filed, but first I'd like to get more coherent STR than a bunch of supposition on my part and relying partially on someone else's server issue that I think might have been fixed not long after I made that post.
Like you say, "Otherwise, we've noticed that a lot of your time (and the developers') gets thrown away on exchanging back and forth to get this information."

I think the only information I'm missing is how to deliberately make a resource (not a subdocument) hang loading on the server side.

EDIT Ok this will do:

Code: Select all

<?php while(true) {} ?>

Formal issue should be filed today or tomorrow.

Post by **barbaz** » Sat May 21, 2016 6:45 pm

gorhill wrote:Could you open a formal issue for this?

Issue opened: https://github.com/gorhill/uBlock/issues/1646

Post by **barbaz** » Mon Jun 27, 2016 3:14 am

Just to clarify before trying to put together another formal issue, is this supposed to be a valid uBlock Origin filter or not?

Code: Select all

||::1^

Not sure if that filter has always caused this since I've use uBlock Origin or if it's a recent regression

Code: Select all

FilterContainer.compileFilter("::1^"): invalid filter static-net-filtering.js:1991:9
FilterContainer.prototype.compileFilter() static-net-filtering.js:1991
FilterContainer.prototype.compile() static-net-filtering.js:1933
µBlock.compileFilters() storage.js:622
µBlock.getCompiledFilterList/onRawListLoaded() storage.js:503
readExternalAsset/reportBack() assets.js:960
readExternalAsset/onExternalFileLoaded() assets.js:983
getTextFileFromURL/onResponseReceived() assets.js:352

gorhill · Post by **gorhill** » Mon Jun 27, 2016 2:20 pm

barbaz wrote:Just to clarify before trying to put together another formal issue, is this supposed to be a valid uBlock Origin filter or not?
Code: Select all
||::1^
Not sure if that filter has always caused this since I've use uBlock Origin or if it's a recent regression

I thought such case should never happen, but then you just proved me wrong. I can add support for this. The problem with such filter is that it can't be tokenized, and this means it will have to be tested for every single network request. (this is also true for regex-based filters, or any filter from which no token can be extracted).

Post by **barbaz** » Mon Jun 27, 2016 2:25 pm

Thanks gorhill for the fast reply. Having support for such filter would be great!

(Not urgent on my count though; if it has to be tested against every network request anyway, I might as well convert it to a regex for now.)

yes_noscript · Post by **yes_noscript** » Thu Jul 28, 2016 10:16 pm

Gorhill did you know about the new Pale Moon 27 (codename Tycho) ?

Your both addons, uBlock & uMatrix works without any problems!
Maybe you like to test it your self.

The PM27 alpha is public: http://www.palemoon.org/WIP/
Info thread: https://forum.palemoon.org/viewforum.php?f=56

Ah and gorhill can you please add the feature to delete cookies after the tab get closed, like the Self-Destructing-Cookie addon?

InformAction Forums

µBlock Origin thread

Re: ublock question

Re: ublock question

Re: µBlock Origin thread

Re: µBlock Origin thread

Re: µBlock Origin thread

Re: µBlock Origin thread

Re: µBlock Origin thread

Re: µBlock Origin thread

Re: µBlock Origin thread

Re: µBlock Origin thread

Re: µBlock Origin thread

Re: µBlock Origin thread

Re: µBlock Origin thread

Re: µBlock Origin thread

Re: µBlock Origin thread