the-gadgeteer.com (whole page blocked) [user]

[Reporter]

Website:
http://the-gadgeteer.com/review/kill_a_ ... tor_review

Problematic Filter (EasyElement):
#*(id^=AdTop)

I have EasyList, EasyElement, ABP Tracking Filter installed.
Please check and confirm.

[LanikSJ]

Works just fine here.

[Ares2]

Firefox 3 -> OK
Firefox 2 -> page hidden

The element is

Code: Select all

DIV(id=adTopBox)

(note the lowercase "a")

It seems that Firefox 3 treats hiding rules case sensitive while Firefox 2 ignores that.

[rick752]

Firefox 3 -> OK
Firefox 2 -> page hidden

Are you serious? Another discrepancy between Fx2 and Fx3 again? Time for Firefox 2 to die!!!!
I know that Firefox has done that before. I think it ignores case sometimes when the element tag is a wildcard.

I saw there was a case difference in that element-hide there, but the page was displaying fine on Fx3 here. I would say just disable #*(id^=AdTop) in the list.

Can someone with Fx2 disable that rule and then see if it still does it with
#DIV(id^=AdTop)
... instead?

I may not do anything about that if that doesn't work because that div would seem to be done on purpose. Let them suffer .

[Ares2]

Can someone with Fx2 disable that rule and then see if it still does it with
#DIV(id^=AdTop)
... instead?

Still hidden, you'll have to kill Fx2.

[rick752]

I just made a new extension called "Hand Grenade for Firefox 2". Everyone should install it ... I give it 5 stars

@Reporter:
Just turn the #*(id^=adTop) string in the element filter.

[Reporter]

Can someone with Fx2 disable that rule and then see if it still does it with
#DIV(id^=AdTop)
... instead?

Still hidden, you'll have to kill Fx2.

Same. the whole page is still blocked.

BTW some users need Fx2 because some extensions are not ready for fx3.

[Hubird]

BTW some users need Fx2 because some extensions are not ready for Fx3.

You can't hold back forever because of a few extensions that are no longer being actively developed and have not be updated for fx3.I've got a feeling that It wont be that long before ABP will not work at all on Fx2.

As far as extensions go, I don't use as many as a some people do (I only use 11) but they way I see it is that ABP is a necessity and the rest are niceties. I'm willing to forgo some of my other extensions to pave the way for ABP improvements.

[rick752]

Same. the whole page is still blocked.
BTW some users need Fx2 because some extensions are not ready for fx3.

Then just disable #*(id^=adTop) in the element filter.

[Ares2]

As far as extensions go, I don't use as many as a some people do (I only use 11) but they way I see it is that ABP is a necessity and the rest are niceties. I'm willing to forgo some of my other extensions to pave the way for ABP improvements.

Same here. I also use 11 extensions ATM and everything that didn't work with Fx3 after the release had to go (but I think I found a replacement for all of them).

@Reporter: If you can't find an updated version of your extensions (or a devbuild etc.) there is still the possibility that they work in Fx3 but haven't been marked compatible. You can do this manually then.