Migration to User-Agent Client Hints API

[isaak654]

Description

You have legacy code that depends on navigator.userAgent.
It's advised to plan the move to the equivalent navigator.userAgentData calls in a later version.

Chromium 100 will be the last version to support an unreduced User-Agent string by default (as well as the related navigator.userAgent, navigator.appVersion, and navigator.platform DOM APIs).

Google Chrome and Mozilla Firefox are both rapidly approaching version 100, which has the potential to break some websites that incorrectly check for the browser version. Both browsers have been working on possible solutions, and now Chrome 100 has arrived in the Beta Channel with changes to version reporting and other new features.

Additional information/references

https://blog.chromium.org/2022/03/chrome-100-beta-reduced-user-agent.html
https://hacks.mozilla.org/2022/02/version-100-in-chrome-and-firefox/
https://www.xda-developers.com/chrome-100-beta/
https://www.xda-developers.com/chrome-firefox-100/
https://web.dev/migrate-to-ua-ch/
https://web.dev/user-agent-client-hints/

[jdarwood007]

https://caniuse.com/mdn-api_navigator_useragentdata

Looks like only chromium based browsers support it. So not wise to support it because then we have to support both methods.

[isaak654]

That could change anytime since Firefox 100 onwards, so it's not that far.

[jdarwood007]

Still leaves Safari which includes iOS.

2 of the files referenced are from 3rd party plugins. The last is ours and we don't make too much use of the user agent anymore. We have been slowly moving away from that. I see some of our code is for supporting IE, which isn't all that important to support nowadays, but it is in the code. I would rather see this bug more about tracking removal of all user agent sniffing in the first place and doing either standards or if needed, feature sniffing.