Chrome phasing out support for User-Agent
1–10 of 329 posts
Re: Chrome phasing out support for User-Agent
#2If they're the dominant web browser people will assume you are using Chrome anyway.
Re: Chrome phasing out support for User-Agent
#3I was wondering. Isn't the page rendered on mobile and desktop based on user-agents? How would that work now?
Re: Chrome phasing out support for User-Agent
#4As usual, this will fuck up the users, and not the techy nerds making such decisions, but the average joe because things on the internet will be broken for them.
Re: Chrome phasing out support for User-Agent
#5I was wondering. Isn't the page rendered on mobile and desktop based on user-agents? How would that work now?
There not phasing out User-Agent strings entirely, they're actually upgrading them:
https://github.com/WICG/ua-client-hints
It looks like there's more fine grained control in the new version.
Re: Chrome phasing out support for User-Agent
#6This was recently discussed on HN:
3 months ago: https://news.ycombinator.com/item?id=21781019
1 year ago: https://news.ycombinator.com/item?id=18564540
Re: Chrome phasing out support for User-Agent
#7I was wondering. Isn't the page rendered on mobile and desktop based on user-agents? How would that work now?
I thought it used Javascript to detect screen size. At least it should react to resize events and if the dimensions are something that align with mobile, it should switch to mobile mode.
Re: Chrome phasing out support for User-Agent
#8As usual, this will fuck up the users, and not the techy nerds making such decisions, but the average joe because things on the internet will be broken for them.
[deleted]
Re: Chrome phasing out support for User-Agent
#9As usual, this will fuck up the users, and not the techy nerds making such decisions, but the average joe because things on the internet will be broken for them.
Give an example.
Re: Chrome phasing out support for User-Agent
#10Because, there can be only one user agent...!