canmove, Confirmed users
1,584
edits
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
Standards: | Standards: | ||
* [http://www.w3.org/TR/touch-events/ W3C Touch Events] | * [http://www.w3.org/TR/touch-events/ W3C Touch Events] (shipped by Safari, Chrome, IE Mobile, Firefox for Android, Firefox OS) | ||
* [http://www.w3.org/TR/pointerevents/ W3C Pointer Events] | * [http://www.w3.org/TR/pointerevents/ W3C Pointer Events] (shipped by IE Desktop, IE Mobile) | ||
** touch-action is part of the Pointer Events spec (shipped by Chrome, IE Desktop, IE Mobile) | |||
Notes: | |||
* Just implementing Touch Events and touch-action (without Pointer Events) would allow efficient Pointer Events polyfills, and other developer benefits (including ability to improve responsiveness of touch UIs). This is what Chrome is currently doing. | |||
* Implementing APZC on desktop would allow desktop Firefox to share much of the Touch Events / Pointer Events / touch-action code with Firefox OS. | |||
** Similarly, porting Firefox for Android to the Gecko APZC and meta viewport code would allow increased code sharing with Firefox OS. | |||
Current work: | Current work: | ||