1423604 - Touchscreen two finger tap right click gesture not available on Windows 7

Status: NEW

(Firefox :: General, enhancement, P5)

Description

[bairdlinde]

What did you do?
================
1. updated to 57? whatever the recent update with the new UI and the performance overhaul was
2. tried to do the usual touch gesture of touching a spot with one finger and tapping with a second finger to perform a right click.

What happened?
==============
nothing

What should have happened?
==========================
a right click menu

Is there anything else we should know?
======================================
it's a built in gesture on windows 7, and now I assume you've taken fuller control of your touch input without reproducing the same behavior. Prior to this update it was the quickest and easiest way to right click to open a link in a new tab or copy a text selection without a mouse or keyboard. I can still do a one-point touch and hold to right click, but this is considerably slower and tends to fight with your new text selection behavior, especially when trying to copy selected text.

Comment 1

[Jim Mathies [:jimm]]

Pretty sure this is something front end would have to implement. We have code down in widget that detects this, but we mark windows as touch friendly now which disables these gestures.

Comment 2

[Panos Astithas (he/him) [:past] (please ni?)]

Philipp, what is your take on this?

Johann, is there a way to implement this only for non-touchscreen-enabled systems?

Comment 3

[(Currently slow to respond) Philipp Sackl [:phlsa] (Firefox UX) please use needinfo]

It looks like Microsoft has removed this behavior in Windows 10 (I don’t have a Windows 7 install here to verify).
Chrome still implements the behavior on Windows 10 though.
Generally, I’m not opposed to implementing this, provided that it doesn’t interfere with other gestures like pan and zoom (which Chrome’s implementation seems to do). There is an open question around how impactful it will be since Microsoft seems to be phasing out that behavior, limiting the number of users who might know about it.

Comment 4

[Johann Hofmann [:johannh]]

Strange that this regressed in 57 for you, didn't we ship touch events (and consequently disable native touch handling) in 52?

I guess we could implement this somehow (if there's no native Windows event for this probably indeed in the frontend), but as there seem to be conflicts with other gestures and considering that Microsoft removed the feature it would only make sense in Windows 7.

So, given that we don't have a team actively looking at this right now and that we don't really have touch support for any platform other than Windows 10, I think is realistically a P5.

Comment 5

[Kartikaya Gupta (email:[e-mail])]

(In reply to Johann Hofmann [:johannh] from comment #4)
> Strange that this regressed in 57 for you, didn't we ship touch events (and
> consequently disable native touch handling) in 52?

57 was the first release where a lot of users got bumped to e10s, and the new touch events stuff had e10s as a prerequisite.

Comment 6

[Johann Hofmann [:johannh]]

(In reply to Kartikaya Gupta (email:[e-mail]) from comment #5)
> (In reply to Johann Hofmann [:johannh] from comment #4)
> > Strange that this regressed in 57 for you, didn't we ship touch events (and
> > consequently disable native touch handling) in 52?
> 
> 57 was the first release where a lot of users got bumped to e10s, and the
> new touch events stuff had e10s as a prerequisite.

Ah, that might be it. Thanks!