Desktop gesture event with trackpads on Chrome and Safari work differently
Reported by
therealm...@gmail.com,
Mar 21 2016
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.37 Safari/537.36 Example URL: http://jsbin.com/cuxopid/1/edit?html,css,js,output Steps to reproduce the problem: This problem applies only to Desktop usage with Trackpads which supports gestures (OS X and Windows only as far as I know). Chrome specification of gesture like pinch to zoom https://bugs.chromium.org/p/chromium/issues/detail?id=289887 is nowhere specified (so far I've only found this bug) and differs completely from Safari 9.1 gesture event https://developer.apple.com/library/mac/documentation/UserExperience/Reference/GestureEventClassReference/index.html#//apple_ref/doc/uid/TP40009353 What is the expected behavior? The expected behavior is that there is a standard which I can rely on. What went wrong? It's complicated to implement two different gesture behaviors for desktop gesture support. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? Yes Chrome version: 50.0.2661.37 Channel: beta OS Version: OS X 10.11.4 Flash Version: Shockwave Flash 21.0 r0 Is there any effort to unify behavior across Chrome and Safari ? Maybe adapt Safari gesture event support?
,
Mar 23 2016
,
Mar 24 2016
If I understand correctly the difference is that: - Chrome: dispatches wheel event on pinch zoom which apps can prevent default on - Safari (since 9.1): dispatches gesture event on pinch zoom I don't think we want to remove the wheel event for pinch zoom. Dispatching gesture events (at the moment Safari only) seems interesting but that I think depends on adding gesture events to a spec. +rbyers@ who has more context here.
,
Mar 30 2016
We've talked about defining a standard gesture API for touchpad for a long time but haven't yet primarily because we know Microsoft and Apple are unwilling to participate in any such standardization due to IP issues. That said, it seems likely that Mozilla would be interested in working with us on a spec (eg. see https://bugzilla.mozilla.org/show_bug.cgi?id=1052253), and there shouldn't be an issue doing it in WICG (or WHATWG). If we wanted to pursue this, I'd suggest we talk with the other vendors and decide between either: 1. specifying an API that's compatible with what Safari has already shipped 2. defining a new simple API (the design is very obvious - just start/change/end events with scale and rotation values). This would be a non-trivial undertaking, so we'd have to be confident in the value. Personally I don't see the value as huge as it's a desktop-specific issue, and likely wouldn't benefit most of our desktop users (on windows on devices without touchpad gestures). If you're interested in seeing us invest in this, please star this issue (but don't add "me too" comments unless you have some new data to provide).
,
Mar 30 2016
,
Mar 31 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 6 2017
It doesn't look like there's a ton of interest in addressing this. Over to Interop to decide what to do with this.
,
Apr 13 2017
I'm going to mark this as WontFix. Given the low interest and high potential hurdles we're unlikely to invest in this any time soon. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by meh...@chromium.org
, Mar 22 2016