3 ms·
There not phasing out User-Agent strings entirely, they're actually upgrading them: https://github.com/WICG/ua-client-hints https://github.com/WICG/ua-client-hi
by fny 7y ago
There not phasing out User-Agent strings entirely, they're actually upgrading them:
https://github.com/WICG/ua-client-hints https://github.com/WICG/ua-client-hints
It looks like there's more fine grained control in the new version.
- timw4mail 7y agoJavascript-only is not an upgrade.
- snazz 7y agoUA strings have never been an accurate indication. If you're not using JS, then you probably have no reason to be sniffing the UA string to detect browser features, since most of those features are JS-related anyway. It's an upgrade for the people who actually need to get an indication of the supported features and APIs of the user's browser. Otherwise, you should be using media queries.
- oefrha 7y agoOne exception: you might want to user sniff IE and serve a completely different version due to all the CSS problems. (I know you can use IE-only comments too, but I’ve been in the situation where making a modern version simultaneously IE9-compatible was just too frigging maddening.)
- Izkata 7y agoA bigger, site-breaking one from further up in this thread: https://news.ycombinator.com/item?id=22685632 https://news.ycombinator.com/item?id=22685632
- Avamander 7y agoDetecting dumb search crawlers, that don't support major features required for my webapp, and displaying a fallback splash has been the only reasonable way I've found.