[Webkit-unassigned] [Bug 133112] Touch-action css property support

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue May 20 16:50:27 PDT 2014


Jacob Rossi [MSFT] <gtjrossi at gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |gtjrossi at gmail.com

--- Comment #8 from Jacob Rossi [MSFT] <gtjrossi at gmail.com>  2014-05-20 16:50:50 PST ---
Just a couple additional thoughts/responses:

Definitely agree that "synthetic" events (esp. click) are far superior for activation behaviors. Other goodness here too like better accessibility.
     * Note that IE11 now uses the PointerEvent interface for click and will even fire it for multi-touch provided you aren't zooming. So we don't really consider it a "synthetic" event in this regard.

Like Patrick says, touch-action doesn't affect whether you a browser alters coordinate accuracy (in fact, such adjustment is out of scope for our working group)

touch-action: manipulation is about restricting touch behaviors to "scrolling and continuous zooming" aka, disabling features like double-tap-to-zoom
     * This in turn enables browsers to optimize out the 300ms delay for synthetic events like click, but isn't technically a required feature of the API

pan-x/pan-y work well for many common "native" experiences like carousel photo galleries, swiping pagination, etc.
     * The working group has discussed additional values like pan-positive-y/pan-negative-y. It's not in the spec or implementations, but we'd love to have you participate in the WG discussion and discuss use cases we should be solving. I'm thinking we'll tackle this in Pointer Events V2, which is on the near horizon.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list