Cool, looks like a nice little addition to me. +Mustaq Ahmed <mus...@chromium.org> and +Robert Flack <fla...@chromium.org> from the Chrome interactions team who are likely code reviewers.
The only real potential debate I see is around the details of the privacy protections. If I understand correctly "per document instance" means that the IDs will even be different across iframes in the same tab, and also when a page is reloaded. Is that right? If so, I can't see how it would be an issue. On Mon, Dec 5, 2022 at 12:49 PM 'Sahir Vellani' via blink-dev < blink-dev@chromium.org> wrote: > Contact emails > > bemat...@microsoft.com, sahir.vell...@microsoft.com > > > Explainer > > > https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/PointerEventDeviceId/explainer.md > > > Specification > > > https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/PointerEventDeviceId/explainer.md > FWIW with my former PointerEvents spec editor hat on, I pinged this issue <https://github.com/w3c/pointerevents/issues/353> on the PointerEvents spec. We've had 'extensions' to the PointerEvents spec in the past, so the PEWG may be amenable to something simple and pragmatic that'll naturally make it into the next official PE spec rather than starting with WICG. But with my Blink API owner hat on, either path is fine. Summary > > As devices with advanced pen input capabilities are becoming increasingly > prevalent, it is important that the web platform continues to evolve to > fully support these advanced features in order to unlock rich experiences > for both end users and developers. One such advancement is the ability for > a device's digitizer to recognize more than one pen device interacting with > it simultaneously. This feature is an extension to the PointerEvent > interface to include a new attribute, deviceId, that represents a > session-persistent, document isolated, unique identifier that a developer > can reliably use to identify individual pens interacting with the page. > > > > > Blink component > > Blink>Input > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EInput> > > > Motivation > > Currently, developers have no way to distinguish between two individual > pens on an ink-enabled digitizer. The existing PointerEvent.id attribute is > implemented in different ways and does not always persist for each ink > stroke or interaction with the screen. Developers can use this change to > have a secure and reliable way to identify individual pen (pointers) > interacting with the screen in order to set specific colors or pen shapes > for each device interacting with the digitizer. > > > > > Initial public proposal > > > https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/PointerEventDeviceId/explainer.md > > > TAG review > > > > > TAG review status > > Pending > > > Risks > > Fingerprinting risks, which will be mitigated by randomizing the ID each > renderer session. > > > Interoperability and Compatibility > > > > *Gecko*: Request for Position: Extending the PointerEvent with Unique > DeviceId Attribute · Issue #715 · mozilla/standards-positions · GitHub > <https://github.com/mozilla/standards-positions/issues/715> > > *WebKit*: Request for Position: Extending the PointerEvent with Unique > DeviceId Attribute · Issue #102 · WebKit/standards-positions · GitHub > <https://github.com/WebKit/standards-positions/issues/102> > > *Web developers*: No signals > > *Other signals*: > > > WebView application risks > > *Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications?* > > None > > > Debuggability > > deviceId will be available via DevTools for front-end debugging. > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ? > > No > We've got automation plumbing for the rest of PointerEvents I believe. Any reason not to add plumbing through WebDriver for this too and an automated WPT test? I suppose the value is pretty low, but IMHO would be nice if it's not too much more expensive than the alternative chromium-only tests. Flag name > > PointerEventDeviceId > > > Requires code in //chrome? > > False > > > Estimated milestones > > No milestones specified > > > > > Link to entry on the Chrome Platform Status > > https://chromestatus.com/feature/5114132234240000 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SA0PR00MB1033E5DE0BDE42239E647E9AFB189%40SA0PR00MB1033.namprd00.prod.outlook.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SA0PR00MB1033E5DE0BDE42239E647E9AFB189%40SA0PR00MB1033.namprd00.prod.outlook.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY8suLmpqGJVZ7pjWmfDGaHzWoEVcXTruYFWMh%3DwWhYywg%40mail.gmail.com.
