You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently PointerEvent.pointerId is used to build DeviceId, however this isn't perfect because the same device can get a new ID when it is disabled during a session. E.g. your mouse is plugged and the unplugged: it will get a new DeviceId. This is especially bad for non-connected (battery-free) pens, which get a new DeviceIdevery time they leave the maximum hover distance.
For this reason a new PointerEvent.persistentDeviceId was introduced, which identifies a specific device by a unique device ID throughout the whole session.
This is supported by default on Chrome since v128.
Currently
PointerEvent.pointerId
is used to buildDeviceId
, however this isn't perfect because the same device can get a new ID when it is disabled during a session. E.g. your mouse is plugged and the unplugged: it will get a newDeviceId
. This is especially bad for non-connected (battery-free) pens, which get a newDeviceId
every time they leave the maximum hover distance.For this reason a new
PointerEvent.persistentDeviceId
was introduced, which identifies a specific device by a unique device ID throughout the whole session.This is supported by default on Chrome since v128.
W3C
Caniuse
WPT
Firefox Standard Positions
WebKit Standard Positions
The text was updated successfully, but these errors were encountered: