-
Notifications
You must be signed in to change notification settings - Fork 22.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify that navigator.userAgentData is not mature #12017
Conversation
Preview URLsFlawsNone! 🎉 External URLsURL: No new external URLs (this comment was updated 2022-01-15 05:14:23.603775) |
c496a9f
to
e19d663
Compare
I thought it was weird to deprecate a feature when the replacement isn't available cross-browser or even standardised! Do you know where it is deprecated? https://html.spec.whatwg.org/multipage/system-state.html#dom-navigator-platform-dev doesn't say anything to that effect. |
There’s been discussion about this elsewhere, but the gist of it is:
Specifically, the spec allows browsers to simply return the empty string for
Further, in general most everything in the
In other words, the spec doesn’t deprecate the features but instead actually normatively defines requirements for them — however, the spec-defined requirements intentionally make the features effectively useless or unreliable to developers. Hence we want to discourage developers from trying to use the features. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the clarification @sideshowbarker !
Fixes #11934