Boyohboyohboyohboy, Wladimir hid it in a mere changelog: As of the newest dev build,
Whitelisting rules now apply to element hiding rules as well. This is huge news and
will get rid of lots and lots of support issues. It works like charm. Yay!
The whitelisting of course has to be a "site whitelisting".
Whitelisting rules now apply to element hiding rules as well
I know .. I saw it earlier. Because it only works during a full sitewide whitelist, it still leaves us with our little 'tricks' to get around anti-adblocking attempts. This definitely has more good than bad about it.
The downside is that at the moment, it can be a problem on Fx3 .... and there is no release of ABP yet with this fix.
Things are getting a bit scattery between ABP and Fx lately ... I sure hopes things finally release and stabilize soon
The downside is that at the moment, it can be a problem on Fx3 .... and there is no release of ABP yet with this fix.
Things are getting a bit scattery between ABP and Fx lately ... I sure hopes things finally release and stabilize soon
"Experience is something you don't get until just after you need it"
Not sure what you mean there Rick. Running the last ABP dev build with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008032116 Minefield/3.0b5pre - Build ID: 2008032116 and it works great.rick752 wrote:The downside is that at the moment, it can be a problem on Fx3 .... and there is no release of ABP yet with this fix.
"If it ain't broke don't fix it."
Then what does Wladimir mean on his "known issues" when he says:
(I will not use Fx3 until it becomes an RC)Element hiding hits are not always registered in Firefox 3, this always prevents whitelisting rules to apply to element hiding
"Experience is something you don't get until just after you need it"
I'm not sure yet. Seeings as Mozilla devs are still playing around with Fx3 things may change still. Beta 5 branched already so in about a month it should go RC.
"If it ain't broke don't fix it."
So Lanik ... you are using 3.0b5pre and have no trouble getting element-hiding rules to whitelist with a site-exception rule. It works here fine on 2.0.0.12
Hmmm .... I wonder what Wladimir means here?
http://adblockplus.org/development-buil ... ox-3-fixes
Hmmm .... I wonder what Wladimir means here?
http://adblockplus.org/development-buil ... ox-3-fixes
"Experience is something you don't get until just after you need it"
I haven't tried it yet but I'm sure the problem exists. I'll test it though when I get an opportunity.rick752 wrote:So Lanik ... you are using 3.0b5pre and have no trouble getting element-hiding rules to whitelist with a site-exception rule.
"If it ain't broke don't fix it."
The problem is that the element whitelisting relies on the hit counting mechanism in case of elements.rick752 wrote:So Lanik ... you are using 3.0b5pre and have no trouble getting element-hiding rules to whitelist with a site-exception rule. It works here fine on 2.0.0.12
Hmmm .... I wonder what Wladimir means here?
http://adblockplus.org/development-buil ... ox-3-fixes
And as reloading a page sometimes doesn't count the hit (bugs about that already exist), the whitelisting
will break as well in such a case.
This is a bug in Firefox and will hopefully be fixed before 3.0 goes final.
Oh. I remember that discussion now. I never noticed that the element-hiding rule hitcounts stopped after the first view until I read that. And THAT is what is causing the whitelist bug?
But doesn't that also do that in Fx2?
But doesn't that also do that in Fx2?
"Experience is something you don't get until just after you need it"