You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The spec says the following regarding changed changedTouches list and touchstart events:
[[
For the touchstart event this must be a list of the touch points that just became active with the current event.
]]
This implies changedTouches can have more than one touch point during touchstart but is that really the case? It seems like during a touchstart event, changedTouches will only have one touch point.
The text was updated successfully, but these errors were encountered:
In chromium I believe we'll never put two new touches in the same touchstart (or touchend event) but this is really just due to the API design of the underlying platforms we run on (where each finger comes as a separate event) and our desire not to buffer start/end events at all. So I see no reason to require separate events (I could imagine doing a small performance optimization to try to merge these).
On iOS however, the underlying API design matches the model of touch events, and sure enough there I can see multiple changedTouches in a single touchstart or touchend event. Here's a test page.
The spec says the following regarding changed changedTouches list and touchstart events:
[[
For the touchstart event this must be a list of the touch points that just became active with the current event.
]]
This implies changedTouches can have more than one touch point during touchstart but is that really the case? It seems like during a touchstart event, changedTouches will only have one touch point.
The text was updated successfully, but these errors were encountered: