- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Dec 2022 15:55:28 +0000
- To: public-pointer-events@w3.org
Great to see the revived interest here! I agree with @RByers and @patrickhlauke re the WICG path until we are done with L3. Let me bring back an old question from @bmathwig above, which I didn't get a chance to comment before: > Do you think there is a backwards compatibility risk by doing it this way? Is there a case where someone would take a dependency on a "new-ID-per-event" system for creating unique SVG strokes? We don't know any use-case like this, and therefore re-purposing `pointerId` (as per the original proposal here) sounds like an equally acceptable solution to me. As @patrickhlauke mentioned, the "MAY" in the current spec would allow this already. Moreover, this could be interpreted as a generalization of the (existing) constant `pointerId` of mouse. Let's discuss this in the WICG repo. -- GitHub Notification of comment by mustaqahmed Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/353#issuecomment-1346776842 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 December 2022 15:55:29 UTC