Adblock Plus and (a little) more

Element Hiding Helper: The first try · 2007-01-08 01:35 by Wladimir Palant

The first development build of the Element Hiding Helper extension (0.9+.2007010800) has been uploaded. This extension is meant to make creating element hiding rules easier, the code to select the element has been adopted from the Aardvark extension. Adblock Plus 0.7.2.3 or higher is required, browser requirements are the same as for Adblock Plus. This extension is still in the early development stages and some features of the final version are missing.

Installation

https://adblockplus.org/devbuilds/

What is there

• Started by the “Select item to hide” menu item in the Adblock Plus icon’s menu or by the Ctrl+Shift+H shortcut key (default value, change extensions.adblockplus.ehh-selectelement_key preference if necessary).
• Point-and-click selection of the element (thanks Aardvark)
• Composition of basic filter rules (domain, tag name and attributes selection possible)
• Filter rule is added to the list automatically

What needs to be done

• Warning if Element Hiding Helper is installed but Adblock Plus is not there (Firefox 2.0 and higher does it automatically)
• Advanced filter composition mode (allows to specify parts of attributes, custom CSS selector parts, attributes of parent/sibling nodes)
• “View source” function from Aardvark
• Preview of the filter’s effects
• Apply the filter to the current window immediately, without a reload

Known issues

• Shortcut key doesn’t work in SeaMonkey
• Element selection in frames doesn’t work
• It is possible to invoke the “wider” function on the “html” node
• If a command fails, it triggers find-as-you-type (if enabled)
• Context menu items are not hidden properly in SeaMonkey

Tags: elemhidehelper development builds

Comment [4]

1. rick752 · 2007-01-08 06:47 · #

   This is a nice, simple interface. Anyone could use it.
   Simply ‘mouseover’ a page element … then select it, and it automatically outputs it into the native ABP element-hiding code and enters it in the filter box.

   Nice first attempt Wladimir. This certainly would make it easier (even for me) as I wouldn’t even have to modify the code for simple hides. This is a great way for ‘beginners’ to get their feet wet with element-hiding too.

   I’ll keep my eyes open for bugs. Excellent job as usual!!!

2. chewey · 2007-01-08 08:07 · #

   This is great! Thanks a lot!

   Minor problem: If “N” is used to narrow an element that can’t be narrowed further, find-as-you-type is invoked instead, leading to seemingly random scrolling jumps. (speaking for SM 1.1 here)

   Reply from Wladimir Palant:

   Yes, it seems Aardvark prevents default action for events even if the command fails, I’ve done it in the same way now. Find-as-you-type shouldn’t interfere now.

3. MonztA · 2007-01-08 16:11 · #

   Amazing! That makes blocking elements a lot easier! Hope to see more (specific) rules in the next versions.

4. alta88 · 2007-01-08 19:51 · #

   This, of course, is brilliant. A giant usability leap forward.

   The dynamic rule update based on domain/attribute selection (and the discovery of elements’ attributes) is nothing short of…elegant. It would be nice to go the other way with domains, eg site.com/forums/php/etc.

   Still have to see about Aardvark’s element selection granularity..

   Perhaps a forum topic to discuss details?

   Reply from Wladimir Palant:

   Yes, please create this topic. I would like to know what you think is missing there.

Commenting is closed for this article.