- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 May 2024 13:30:15 +0000
- To: public-pointer-events@w3.org
While discussing the concerns, this seemed like a neat way to avoid having a second identifier with slightly different semantics and a convenient way for developers to use it without having to create a map of their own. > My understanding is that .deviceProperties will only be created for the devices with persistent IDs. @ogerchikov Yes, that's correct. > It's possible that we'll need to collect other hardware properties from the devices that don't have persistent IDs, and as a result, they won't have .deviceProperties instantiated. Is there something I'm overlooking? If this information is not associated with a uniquely identifiable pointer, then it wouldn't belong in deviceProperties. If it is, then presumably it wouldn't be known until the persistent id was also known, right? -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/pull/495#issuecomment-2127115616 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 May 2024 13:30:16 UTC