- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jan 2024 18:12:05 +0000
- To: public-pointer-events@w3.org
> therefore re-purposing pointerId (as per the original proposal here) sounds like an equally acceptable solution to me I don't think re-purposing pointerId works because pointerId is expected to remain fixed for a given pointer but the [hardware limitations](https://github.com/WICG/pointer-event-extensions/blob/main/pointer-event-device-id-explainer.md#limitations-of-current-hardware) suggest that for many devices the hardware id is not known until after it starts moving on the surface, and as such the device id would be -1 on the event stream until the point at which the hardware id is known. I think we should discuss this proposal again at the PEWG. It has been implemented with a [draft spec PR](https://github.com/w3c/pointerevents/pull/495), and a [proposal to ship in chromium](https://groups.google.com/a/chromium.org/g/blink-dev/c/3eU-AHH8x4k/m/rCyxcYnQAgAJ). -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/353#issuecomment-1906641207 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 January 2024 18:12:12 UTC