Reduce Gecko's User-Agent strings
Categories
(Core :: Networking, enhancement, P3)
Tracking
()
People
(Reporter: emk, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: dev-doc-needed, Whiteboard: [necko-triaged])
Chrome announced the timeframe. Safari already froze the user-agent header (except OS version and browser major version).
|
||
Comment 1•5 years ago
|
||
This seems to depend on User Agent Client Hints.
|
Reporter | |
Comment 2•5 years ago
|
||
I'm surprised that the Client Hints proposal has been around for a very long time.
|
||
Updated•5 years ago
|
|
||
Comment 3•5 years ago
|
||
(In reply to Masatoshi Kimura [:emk] from comment #0)
Chrome announced the timeframe. Safari already froze the user-agent header (except OS version and browser major version).
I'll just note that Firefox has shipped with support for this since FF58 (Bug1333651), although behind a pref. Tor Browser has frozen its UA string (except moving between ESR versions and OS) for most of the last decade (originally via the |general.*.override| prefs).
|
||
Comment 4•5 years ago
|
||
See Mozilla's position here - https://github.com/mozilla/standards-positions/issues/202#issuecomment-558294095.
|
||
Updated•3 years ago
|
|
||
Updated•2 years ago
|
|
||
Comment 5•1 years ago
|
||
When Firefox's User-Agent string is changed, we should also update the UA Compatibility spec:
Description
•