Intent to Deprecate and Freeze: The User-Agent string
User-Agent sniffing, used for example to (try to) perform dynamic serving instead of true responsive web design, has always been a really bad practice, for different reasons:
The User-Agent string is an abundant source of passive fingerprinting information about our users. It contains many details about the user’s browser and device as well as many lies ("Mozilla/5.0", anyone?) that were or are needed for compatibility purposes, as servers grew reliant on bad User-Agent sniffing.
On top of those privacy issues, User-Agent sniffing is an abundant source of compatibility issues, in particular for minority browsers, resulting in browsers lying about themselves (generally or to specific sites), and sites (including Google properties) being broken in some browsers for no good reason.
(Did you see this "including Google properties"? 😉)
Evolution of this intent can be tracked in Chrome Platform Status.
If you want to share an error or suggest an enhancement of this content, please edit the source on Github.