Re: [w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27)

Yes, there are no concerns with increasing the range of touchId. I'll change it to an unsigned long. I'll also make it clearer that the user agent should increase the touch id from 0 to the max value before rollover occurs.

> The proposal doesn't describe how touch events are associated with a touch ID.

The intent was for the user agent to assign the touch ID associated with each touch event based on information from the device API. This would be needed since different devices may output a different range of touch ids. Additionally, we've seen devices report touch up differently. Some explicitly indicate the event has occurred, while others cease updates for a touch ID.

I'll add that clarification to the proposal as well.

> Could we support a device that only provides touch coordinates and no tracking?

I think what you're asking here is whether we can support a device that doesn't indicate a touch down/up has occurred in any of the aforementioned ways. We could support that type of device by having the user agent assign a touch id of 0 to all touch events.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/27#issuecomment-359510643