Page 1 of 1

Disabled element hiding filters invisible in blockable items

Posted: Fri Dec 05, 2008 3:03 pm
by Wladimir Palant
Moved from http://adblockplus.org/forum/viewtopic.php?t=3207:
Adblock Plus Fan wrote:On a minor note, elements matching disabled element hiding rules still just disappear.
Wladimir Palant wrote:You are the second one to say that - do you have an idea how to reproduce that issue? Note that element hiding can no longer be unapplied - if you disable a filter you need to reload the page.
Adblock Plus Fan wrote:WinXP sp3
Java 1.6.0_07
Adobe Flash 10.0 r12
Firefox 3.0.4
New firefox profile.

Install dev. build: adblockplus-1.0.0+.2008120323-en-US.xpi
Restart
Add filter: adblockplus.org#DIV(id=content)
Go to: http://adblockplus.org/en/
Disable filter from Blockable items list
Reload http://adblockplus.org/en/

No trace of the DIV or its filter in the blockable items list.



EDIT: I have also tried to disable those 2 plugins from the Add-ons menu and restarted.
Same result.

Posted: Fri Dec 05, 2008 4:06 pm
by Wladimir Palant
Tried these steps in both Firefox 3.0.4 and Shiretoko with different variations - no success, everything works for me. Maybe I am missing some detail?

Are you adding the filter in Preferences? Is the list sorted? Do you have other element hiding filters/other filters? Do you have a filter subscription? Which one?

Posted: Fri Dec 05, 2008 4:48 pm
by Adblock Plus Fan
Yikes....Looking at the title of this thread, I think we had a misunderstanding.
I can see now that I worded it too stupidly:
elements matching disabled element hiding rules still just disappear (from the blockable items list)
What I really meant was, after disabling an element hiding rule, I expected to see this:
Image
And expect it to stay that way.
But instead, the filter isn't there in the blockable items list after a reload:
Image

So uh....sorry about that :?

Posted: Sun Dec 07, 2008 1:53 pm
by Wladimir Palant
Heh, there is really no way to indicate element hiding rules that didn't have a hit... Guess that isn't a bug after all.

Edit: Fixed thread title.