[Feature Request] Add "Zapp this element..." or "Enter element zapper mode" to right click context menu

[GlassGruber]

Prerequisites

• I verified that this is not a filter list issue. Report any issues with filter lists or broken website functionality in the uAssets issue tracker.
• This is NOT a YouTube, Facebook or Twitch report. These sites MUST be reported by clicking their respective links.
• This is not a support issue or a question. For support, questions, or help, visit /r/uBlockOrigin.
• I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
• The issue is not present after disabling uBO in the browser.
• I checked the documentation to understand that the issue I am reporting is not normal behavior.

I tried to reproduce the issue when...

• uBO is the only extension.
• uBO uses default lists and settings.
• using a new, unmodified browser profile.

Description

Since there is an item for "Block this element..." in context menu, an additional element for "Zapp this element..." or "Enter element zapper mode" (or maybe both?) could be a useful addition.

Incidentally "Zapp this element..." this could also partially fix #3594, since the action would zapp only target element.
I think this could be a beneficial addition also for impaired users as I am, where using both hands to fire the shortcut could be difficult.

Sorry to use an issue ticket, I wasn't able to find a more suitable place for feature requests.

Thank you uBO team for your time and effort and for this invaluable tool!

A specific URL where the issue occurs.

https://github.com/gorhill/uBlock/wiki/The-context-menu

Steps to Reproduce

There is no right click action for zapper mode or "Zapp this element" in context menu.

Expected behavior

A right click action for zapper mode in context menu.

Actual behavior

There is no right click action for zapper mode or "Zapp this element" in context menu.

uBO version

1.67.0

Browser name and version

Firefox 145.0.2

Operating System and version

Windows

[gorhill]

You can assign and use a keyboard shortcut to launch zapper.

[freezer2022]

But OP already mentioned that a keyboard shortcut is not comfortable for users like him:

GlassGruber: I think this could be a beneficial addition also for impaired users as I am, where using both hands to fire the shortcut could be difficult.

[gorhill]

Right, I need to read more carefully.

[GlassGruber]

Thank you freezer2022 and gorhill for your answers

Right, I need to read more carefully.

No worries, really ;)
I can't imagine how many things you all have to take care about, and I'm sorry I wasn't able to find a better place to open a feature request. Also I wasn't expecting for having an answer back so quickly, this is indeed a minor grade issue, so thank you for your time!

Regarding the shortcut issue per se: while browsing I do find myself most of the time with one hand on the mouse, the other is generally near the keyboard but not always.

So for the occasional annoying buzzing single element or whatever, I think that right clicking on it is quicker and more convenient than using a shortcut since my hand is already on the mouse scrolling the page, etc. Does that make any sense?

[freezer2022]

GlassGruber : So for the occasional annoying buzzing single element or whatever

If you meant to instant hide the clicked element when using "Zapp this element" in context menu, then that is not good, because blindly hiding an element without seeing it highlighted first, might result in hiding a wrong element. That's why Picker and Zapper always highlight an element before allowing an user to finally click and hide it.

GlassGruber : Since there is an item for "Block this element..." in context menu, an additional element for "Zapp this element..." or "Enter element zapper mode" could be a useful addition.

Yes, even without instant hiding, adding "Zapp this element" to context menu seems logical given there already exists "Block this element", as existence of only one of them is inconsistent.

[GlassGruber]

freezer2022: If you meant to instant hide the clicked element when using "Zapp this element" in context menu, then that is not good.

Absolutely agree, what I would have expected is something like you mentioned right after, highlighting the right click target element waiting for the click/zapp.

[krystian3w]

Browser name and version

Firefox 145.0.2

Theoretically you can use the Fx (functional) keys, empty are e.g. (or easily disable their default functionality from about:config):

F1, F2, F4, F8

If you don't mind activating the address bar, you should be able to use F6 (I haven't checked if it can be unbind in stable releases from about:config).

F6 might be freed from the address bar in a few months on the new about:keyboard.

Then the only limitation is whether you can move that one hand from the mouse to the keyboard and vice versa (when the other hand is non-existent or too weak to press something).

---

Unfortunately, this will not work when you change the browser to Chromium, maybe also Safari (uBoL) and when pressing e.g. Fn 🟦 is required to unlock the standard function key signal (the default MacBook keyboard has some functionality on that row of keys when you don't have a touch bar, probably similar for iMacs).

Perhaps under Chromium it is possible to create an alias in an AutoHotKey or AutoIt script.

[u-RraaLL]

Personally, I wouldn't want to have that item in my context menu, but I do understand its usefulness for some. If added, I'd like a "Disable Element Zapper in context menu" item added under "Make use of context menu where appropriate".

Another idea would be to just have the one button that already exists. Keep left button click to launch picker, as usual, but allow launching zapper by scroll/middle clicking it instead.

[krystian3w]

Theoretically, you can then use it in userChrome.css (toolkit.legacyUserProfileCustomizations.stylesheets):

/* if ‘zap’ will be used */
menuitem#ublock0_raymondhill_net-menuitem-_uBlock0-zapElement { display: none !important }

/* if only ‘zap’ appears without a permanent ID in the context menu */
menuitem[id^="ublock0_raymondhill_net-menuitem-_uBlock0-"]:not(
[id*="blockElement"], [id*="viewSource"], [id*="subscribeToList"]
) { display: none !important }

Chromium or Orion are worse, because they don't really have such features, with the possible exception of Vivaldi (in Vivaldi, someone would need to check whether CSS modifications have access to the context menu).