Open Bug 1954132 Opened 1 month ago Updated 1 month ago

Click and Hold for Context Menu with Pen Input

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

Firefox 136
defect

Tracking

()

UNCONFIRMED

People

(Reporter: toprakceceli, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.0

Steps to reproduce:

"ui.click_hold_context_menus" in about:config is set to false like default.
Windows Ink's own "press and hold to right click" option is off.
With a pen input i.e. a stylus on a drawing tablet (in my case a Wacom Intuos Pro), click and hold.

Actual results:

The cursor has a small deadzone where the pointer won't move, context menu shows up upon raising the stylus in the deadzone.

Expected results:

No deadzone occurs, context menu doesn't show up.

This issue causes short pen inputs to not register and for longer pen inputs to have a stutter as they start. A possible solution I've found was to turn off "Use Windows Ink" in Wacom Tablet Properties, but that prevents Firefox from using pressure sensitivity.
I have confirmed this is a Firefox issue as no deadzone occurs in any other program.

Not sure if this is the right component. If not, please move.

Component: Untriaged → DOM: UI Events & Focus Handling
Product: Firefox → Core

Kagami, I noticed you've touched pen code. Do you have an idea of what's happening here?

Flags: needinfo?(krosylight)

Windows Ink's own "press and hold to right click" option is off.

I don't think individual apps can detect this. It would only affect apps that do not handle the pointers directly, but browsers do handle it directly.

One workaround is to set dom.w3c_pointer_events.scroll_by_pen.enabled=false, which will stop APZ from opening a context menu by pen (but this also causes other behavior change).

This issue causes short pen inputs to not register and for longer pen inputs to have a stutter as they start.

This is a separate problem: bug 1716355.

Flags: needinfo?(krosylight)
Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.