Make WordPress Core

Opened 5 years ago

Last modified 4 years ago

#49198 assigned enhancement

Blink: Intent to Deprecate + Freeze `navigator.userAgent`

Reported by: georgestephanis's profile georgestephanis Owned by: adamsilverstein's profile adamsilverstein
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: javascript Cc:


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:

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:

Change History (3)

#1 @ehtis
4 years ago

Client Hints can be tested in Chrome 84 beta.

Also, re. the traditional User-Agent string format:

First, the phase of the project that reduces the amount of available information in the traditional User-Agent string to browser (e.g. “Chrome”), major browser version, and mobile/desktop, has been deferred until at least 2021 to provide additional time for the ecosystem to evaluate the new UA-CH capabilities.


#2 @adamsilverstein
4 years ago

  • Owner set to adamsilverstein
  • Status changed from new to assigned

#3 @adamsilverstein
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:

Note: See TracTickets for help on using tickets.