Support Client Hints
Opened this issue · 9 comments
Google Chrome's developer tools shows a hint about the usage of navigator.userAgent and navigator.userAgentData. More info: Migrate to User-Agent Client Hints
@BenjaminAbt do you have more info if we need to take this into account?
If I understand the navigator thing right, thats a JavaScript DOM API and does not affect requests / our impl.
but maybe we have to update this
Windows 11 Chrome
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.63 Safari/537.36
Windows 11 Edge
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.63 Safari/537.36
Cannot see any changes regarding Win11
But there is this doc
https://docs.microsoft.com/en-us/microsoft-edge/web-platform/how-to-detect-win11
I guess I have to test this
I cannot see any Header Changes in the Developer Tools in Chrome, Edge oder Brave.
Edit: I can see changes in Chrome. I was watching the wrong tab before.
User AGent is still present
In Brave:
No new tags
In Edge same as Chrome
I would suggest we change our behavior: first check the new headers.
Then the user agent.
I would suggest we change our behavior: first check the new headers.
Then the user agent.
Sounds like a good plan.
There is now a documentation
https://developer.mozilla.org/en-US/docs/Web/HTTP/Client_hints#user-agent_client_hints
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-CH-UA#browser_compatibility
but still not implemented in all browsers
Due to privacy reasons we still do not have client hints in all major browsers
https://www.whatismybrowser.com/detect/client-hints/faq/which-web-browsers-support-client-hints