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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue May 20 07:20:42 PDT 2014


Rick Byers <rbyers at chromium.org> changed:

           What    |Removed                     |Added
                 CC|                            |benjamin at webkit.org,
                   |                            |rbyers at chromium.org

--- Comment #2 from Rick Byers <rbyers at chromium.org>  2014-05-20 07:21:05 PST ---
FYI there are several reasons we decided to add touch-action to blink.  Eg. from https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/sc5lHnlcLvM/ntJWuKKHUqYJ: 

 1. Provides precise control over the dreaded 300ms click delay on mobile
 2. Reliably enables side-swipe UIs (frees libraries from having to predict when exactly scrolling may start on different browsers)
 3. Enables high-fidelity polyfills of pointer events (eg. as in Polymer)
 4. Provides a declarative signal to blink (and potentially the compositor) about the developers intent wrt. touch input - eg. providing a potential solution the touchstart ACK timeout problem
 5. Reducing confusion around the highly-overloaded response to preventDefault on touch events
 6. A prerequisite for future optimizations to enable scrolling and zooming that never block on the main thread

It's #5 that seems to resonate most with typical web developers.  In particular I continue to see developers struggle with implementing side-swipe UIs (#2), and I believe mobile safari requires them to reverse-engineer a magic distance threshold number (which then imposes a compat burden on the web no to change that magic value).

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