- From: smaug---- via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 May 2024 15:57:23 +0000
- To: public-pointer-events@w3.org
We were discussing this today and one approach which gets rid of the id altogether and also handles the example in the current pr without need to have explicit hashtable around is to have basically an empty DeviceProperties interface (or perhaps it should be called something else), but it is guaranteed that the same object is returned from .deviceProperties for the same device. The value would be null if there isn't a relevant device. Now the web site could attach random properties directly to that object, for example event.deviceProperties?.myFrameworkColor = "#FFFFFFFF"; and that property would stay there, since the deviceProperties object is kept alive. This does mean that UA needs to keep some objects alive (if there are expando properties), but that isn't too different to all the stuff hanging for example from window.navigator. -- GitHub Notification of comment by smaug---- Please view or discuss this issue at https://github.com/w3c/pointerevents/pull/495#issuecomment-2125147832 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 May 2024 15:57:24 UTC