Gecko/Touch: Difference between revisions

62 bytes removed ,  9 December 2014
update planning section
(other browser status)
(update planning section)
Line 1: Line 1:
== Status in Gecko ==
This table summarizes some of the broad features related to touch input on the web, and their implementation status on different Gecko platforms:
This table summarizes some of the broad features related to touch input on the web, and their implementation status on different Gecko platforms:


Line 19: Line 21:
| Windows metro  || yes          || yes (disabled)        || yes                  || Gecko APZC            || Gecko
| Windows metro  || yes          || yes (disabled)        || yes                  || Gecko APZC            || Gecko
|}
|}
== Status in other browsers ==


This table lists support by other browsers as of December 2014:
This table lists support by other browsers as of December 2014:
Line 34: Line 38:
| Safari || ✓ ||  ||   
| Safari || ✓ ||  ||   
|}
|}
== References ==


Standards:
Standards:
Line 41: Line 47:
** touch-action is part of the Pointer Events spec (shipped by Chrome, IE Desktop, IE Mobile)
** touch-action is part of the Pointer Events spec (shipped by Chrome, IE Desktop, IE Mobile)


Notes:
== Planning ==
 
* 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:


* '''Windows metro''': Finish Pointer Events / touch-action as reference implementation for W3C spec (MS Open Tech).
* '''Mac''': Use async pan/zoom (gfx).
* '''Windows desktop''': Fix and enable Touch Events, and implement Pointer Events / touch-action (MS Open Tech, Platform Integration?).
* '''Windows desktop''': Fix and enable Touch Events, and implement Pointer Events + touch-action (MS Open Tech, Platform Integration?).
* '''Firefox OS''': Implement and enable pointer events / touch-action (MS Open Tech?).


Possible future priorities:
Possible future work:


* '''Firefox OS''': Implement and enable pointer events and/or touch-action (MS Open Tech?).
* '''Android''': Implement Pointer Events and/or touch-action.
* '''Android''': Unify Android and Gecko APZC and viewport code.
* '''Android''': Unify Android and Gecko APZC and viewport code.
* '''Android''': Implement Pointer Events / touch-action.
* '''Windows/Linux desktop''': Use async pan/zoom ({{bug|apzc-desktop}}).
* '''Mac''': Implement async pan/zoom for trackpad gestures.
* '''Windows desktop''': Implement async pan/zoom for touch-screen and trackpad gestures.
* '''Platform''': Implement CSS Device Adaptation to rationalize mobile viewport code ({{bug|747754}}).
* '''Platform''': Implement CSS Device Adaptation to rationalize mobile viewport code ({{bug|747754}}).
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.
canmove, Confirmed users
1,584

edits