Confirmed users
371
edits
(→Plan) |
|||
Line 33: | Line 33: | ||
=== Plan === | === Plan === | ||
* Work on our Events implementation to get them close to a possible spec (following smaug's proposal?) | |||
* Get rid of the manual document.multitouchData switch and work on switching modes when the page requests any touch events | |||
* Sync with mobile's needs | |||
** This will deactivate page scrolling and win7 gesture recognition | |||
* [LAND 1] Deliver the raw events input first | |||
* Check on using windows gesture processors or implement our own gesture engine | |||
* [LAND 2] Deliver the gesture events | |||
* Re-implement [kinetic] panning on our engine for the pages using the touch events | |||
* [LAND 3] Deliver panning on our engine | |||
Note 1: for pages that will not make use of the touch apis, nothing will change, and we will continue to use window's own gesture and scrolling processors. If, after LAND 3 or later we think our own stack is good enough to replace windows's one we can make the full switch | |||
Note 2: Most demos out there related to touch (e.g. [http://scripty2.com/demos/touch/]) never combine it with a page with scrolling, so disabling it as a first step doesn't seem to be a big problem. |