Confirmed users
371
edits
Firefox/Projects/Multitouch Polish/DOM Events: Difference between revisions
Jump to navigation
Jump to search
Firefox/Projects/Multitouch Polish/DOM Events (view source)
Revision as of 17:30, 13 August 2009
, 13 August 2009no edit summary
mNo edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
* '''MozTouchRelease''' | * '''MozTouchRelease''' | ||
Currently they inherit from MouseEvent and adds a '''streamId''' property which uniquely identifies a tracking point. In Win7 this id is provided by the OS/driver layer and is valid only while the same touch point is being tracked. After | Currently they inherit from MouseEvent and adds a '''streamId''' property which uniquely identifies a tracking point. In Win7 this id is provided by the OS/driver layer and is valid only while the same touch point is being tracked. After the finger is released, the id can be (and ''will be'') reused. | ||
Each event is related to each single touch point, so if there are 3 fingers touching the screen, 3 MozTouchMove events can possibly be dispatched for each loop in the message loop. | Each event is related to each single touch point, so if there are 3 fingers touching the screen, 3 MozTouchMove events can possibly be dispatched for each loop in the message loop. | ||
| Line 24: | Line 24: | ||
== Question to ask == | == Question to ask == | ||
==== Aggregated values ==== | |||
For some applications, getting the information for all of the touch points at the same time is important. We send separate events for each touch, so this information is not directly available. But it can be easily supported by a simple JS library which keep track of the current active points. Do we leave it simple and let a JS library do the work if needed? Or should we make this information always available? | |||
==== Compatibility with webkit ==== | |||
Webkit implemented some multitouch events on the iPhone which will be on Android as well. How should we take these into account? Their model is quite different from the typical event model, as in they provide the list of all touches on a single event, and then values like event.clientX and such doesn't exist. Also there are three lists with different rules for the target nodes, some of which keep sending events to original target and this can break the model if there are dynamic changes on the page | |||
==== Gestures and touch ==== | |||