Contact emails
gerch...@microsoft.com<mailto:gerch...@microsoft.com>, 
sahir.vell...@microsoft.com<mailto: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

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>

TAG review
https://github.com/w3ctag/design-reviews/issues/880

TAG review status
Pending. TAG review has been pending for 2 months.

Risks


Interoperability and Compatibility


Gecko: No signal (https://github.com/mozilla/standards-positions/issues/715)

WebKit: No signal (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


Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, 
Chrome OS, Android, and Android WebView)?
No

Is this feature fully tested by 
web-platform-tests<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
No. However, there are web tests in Chromium that test PointerEventInit with 
this feature.

Flag name on chrome://flags
PointerEventDeviceId

Finch feature name


Non-finch justification
Edge origin trials successfully underway.

Requires code in //chrome?
False

Measurement
PointerEventDeviceId use counter implemented.

Availability expectation
Initially available on Chromium browsers on Windows.

Adoption expectation
Feature is used by specific partner(s) to provide functionality immediately 
upon launch.

Adoption plan
This feature has been through origin trials on Edge. It is being used by 
partners that provide features on devices with multi pen support.

Non-OSS dependencies

Does the feature depend on any code or APIs outside the Chromium open source 
repository and its open-source dependencies to function?

Operating system API's are used to obtain the device id, and are necessary for 
this feature to function. Please see the security questionnaire in the TAG 
review on security and privacy concerns related to the use of these APIs.

Estimated milestones
Shipping on desktop
120


Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop 
issues. Please list open issues (e.g. links to known github issues in the 
project for the feature specification) whose resolution may introduce web 
compat/interop risk (e.g., changing to naming or structure of the API in a 
non-backward-compatible way).

WICG Proposal: https://github.com/WICG/proposals/issues/101 No web 
compat/interop risk.

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5114132234240000

Links to previous Intent discussions
Intent to prototype: 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SA0PR00MB1033E5DE0BDE42239E647E9AFB189%40SA0PR00MB1033.namprd00.prod.outlook.com

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/PH0PR00MB1349B7917876E7AC505E790AFBCBA%40PH0PR00MB1349.namprd00.prod.outlook.com.

Reply via email to