Skip to content

Conversation

@jparismorgan
Copy link
Contributor

This article suggested some user agent parsing libraries would have issues with Chrome, Firefox, and Edge browsers with major version 100: https://www.theverge.com/2022/2/17/22938721/chrome-firefox-edge-version-100-websites-bug-compatibility-issues-mozilla-google-microsoft

I went to each, turned on the flag in settings to force the user agent to be 100, recorded the user agent, and then tested that we still recover the browser name, version, and major version successfully. Based on this testing things look okay.

Copy link

@dattanchu dattanchu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we merge the upstream browser-test here instead?

@raido
Copy link

raido commented Feb 22, 2022

My understanding is this will work until Chrome 107 - https://blog.chromium.org/2021/09/user-agent-reduction-origin-trial-and-dates.html - after that user agent string will be with reduced information and from that point forward folks should rely on navigator.userAgentData ie. the User Agent Client Hints - https://web.dev/user-agent-client-hints/

Feature request for Client Hints -> #408

@faisalman faisalman merged commit 6e39c8a into faisalman:master Feb 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants