Ready for Trial: Read Chrome device attributes

Skip to first unread message

Anqing Zhao

Feb 5, 2021, 9:00:20 PM2/5/21

Contact emails





Managed Device Attributes Web API is a subset of Managed Device Web API, that provides to web applications the capability to query device information (device ID, serial number, location, etc).

Blink component


TAG review

TAG review status


Interoperability and Compatibility

Gecko: No signal
WebKit: No signal
Web developers: No signals

Goals for experimentation

Make sure that the API works as expected and can fulfill the target requirement. (Please follow the guide in the file.)

Ongoing technical constraints

This API is available only when the following feature flags are turned on in the chrome://flag page.
  • enable-experimental-web-platform-features: enables experimental Web Platform features that are in development.
  • enable-restricted-web-apis: enables the restricted web APIs for the 'Dev Trials' stage.

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

No. At this stage, this feature is only supported on the Chrome OS.

Is this feature fully tested by web-platform-tests?


Tracking bug

Link to entry on the Chrome Platform Status

Links to previous Intent discussions

Intent to prototype:

Mike Taylor

Feb 7, 2021, 2:57:13 PM2/7/21
to Anqing Zhao, blink-dev
Hi Anqing,

On 2/5/21 4:54 PM, Anqing Zhao wrote:
> Explainer
> <>

I took a peek at the explainer and noticed that this API adds a `device`
to the Navigator interface.

This may or may not be problematic in the future, as Apache Cordova
(formerly Phonegap) had a `navigator.device.capture` API offered through
a plugin[1]. I'm not sure how much of that leaked onto the web (as the
intended target is native mobile apps, but something to be aware of in
case origins who enable this API report issues.



Anqing Zhao

Feb 23, 2021, 4:35:07 AM2/23/21
to Mike Taylor, blink-dev
Hey Mike. Thanks for sharing this link and pointing out the potential conflict. Besides other similar considerations, we are thinking of using `navigator.managed` as the interface name. The related discussion is located at Please feel free to leave a message or let me know if you have a better idea.
Reply all
Reply to author
0 new messages