Open Bug 1609304 Opened 5 years ago Updated 14 days ago

Reduce Gecko's User-Agent strings

Categories

(Core :: Networking, enhancement, P3)

Unspecified
Android
enhancement

Tracking

()

People

(Reporter: emk, Unassigned)

References

(Depends on 2 open bugs, Blocks 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).

This seems to depend on User Agent Client Hints.

Priority: -- → P2
Whiteboard: [necko-triaged]

I'm surprised that the Client Hints proposal has been around for a very long time.

Depends on: client-hints

(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).

Severity: normal → S3

When Firefox's User-Agent string is changed, we should also update the UA Compatibility spec:

https://compat.spec.whatwg.org/#ua-string-section

Severity: S3 → N/A
Summary: Freeze user-agent strings → Reduce Gecko's User-Agent strings
Depends on: 1865766
OS: Unspecified → Android
You need to log in before you can comment on or make changes to this bug.