Opened 5 years ago
Last modified 4 years ago
#49198 assigned enhancement
Blink: Intent to Deprecate + Freeze `navigator.userAgent`
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Future Release | Priority: | normal |
Severity: | normal | Version: | |
Component: | General | Keywords: | |
Focuses: | javascript | Cc: |
Description
https://groups.google.com/a/chromium.org/forum/m/#!msg/blink-dev/-2JIRNMWJ7s/yHe4tQNLCgAJ
It seems there's intent to freeze the navigator.userAgent
functionality from the blink dev team, in favor of the User-Agent Client Hints
functionality as documented here: https://wicg.github.io/ua-client-hints/
Starting an issue here to discuss what (if anything) we'll need to do to handle how WordPress parses and works with user agent strings.
subsequent hn discussion thread: https://news.ycombinator.com/item?id=22044057
Change History (3)
#3
@
4 years ago
- Milestone changed from Awaiting Review to Future Release
Thanks for opening this ticket @georgestephanis - I agree we should be paying attention to this, and may eventually need to update all use in core of navigator.userAgent
.
For now, it seems like most core use will continue to work even with the reduced userAgent information discussed at the bottom of the ticket thread, because we only look for the browser name in nearly all cases: https://github.com/WordPress/wordpress-develop/search?p=3&q=navigator.userAgent
Client Hints can be tested in Chrome 84 beta.
Also, re. the traditional User-Agent string format:
Source