#4039 - UA-client-hints specification, Sec-CH-UA (user agent string deprecation) (on hold)
-
By Chris Graham
- Added
- 2 views
| Identifier | #4039 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | UA-client-hints specification, Sec-CH-UA (user agent string deprecation) (on hold) |
| Status | Open |
| Tags |
Roadmap: Over the horizon (custom) Type: Standards compliance (custom) |
| Handling member | Deleted |
| Addon | core |
| Description | Google is pushing for getting rid of the old UA string, over the next few years.
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/-2JIRNMWJ7s/yHe4tQNLCgAJ It's not so bad for now, as they are just freezing the string, but eventually it will probably be removed entirely - in which case we need to plan for that. At this stage it is very early, and I raised some issues with their specifications: https://github.com/WICG/ua-client-hints/issues/14 Update tut_webapp to reference the spec. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
It looks like their progress has stalled and they've sailed way past their aggressive timeline.
Also, the major version of web browsers is apparently going to stay even when the UA header is stalled. "Note that the User-Agent significant version will continue to be updated.".
The mobile info will be included in what is frozen.
So it seems the urgency of all this is much less of an issue now.
We are now using the standard tangentially within #4962.
If we were to use it more, we would...
- Make browser detection addon use it
- Make our stats collection preferentially use it
- Use Sec-CH-UA-Mobile being "?1" in the is_mobile function