- From: Sahir Vellani via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 May 2024 18:06:12 +0000
- To: public-pointer-events@w3.org
I don't want to force `event.deviceProperties.uniqueId` through just because we switched to it in Chromium. Ideally everyone would be happy with the solution; as this impacts the future of one of the most popular web APIs. That being said, it would be great if we could all work together towards a consensus _ASAP_. We have received positive feedback from our web developer partners on both forms of the API. My humble 2 cents: Could we mandate in the spec that `deviceProperties` always exists with a default value of an invalid `uniqueId`? That way we can still differentiate between device-specific and pointer-specific properties like @smaug---- and @flackr were initially concerned about without the additional `null` check that @annevk mentions. -- GitHub Notification of comment by sahirv Please view or discuss this issue at https://github.com/w3c/pointerevents/pull/495#issuecomment-2118137583 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 May 2024 18:06:13 UTC