3 ms·
That might make sense for some cases, but honest to God, it's usually not worth it. First of all, you have to make a warning pretty ridiculously blatant before
by jchw 9y ago
That might make sense for some cases, but honest to God, it's usually not worth it.
First of all, you have to make a warning pretty ridiculously blatant before people actually will even read it. Most people skip right past red and yellow boxes, and nobody ignores browser support warnings better than IE users.
Secondly, then once users decide to ignore anyways, they clog up your support. At Google scale, that is probably a serious monetary difference. For most companies, it's just frustrating to the support staff and a general waste of limited time. Even if your warnings work, some users don't know enough and assume that the default web browser can't be wrong. You may even find someone who swears up and down they use Chrome (or perhaps just 'Google,') but actually they're on Edge, maybe even by accident.
A lot of web best-practices are focused on developers and not end users. Sometimes they're at odds with each-other. For example, the large portion of users on IE are a bigger concern than the almost unobservably small portion on browsers that would work but get UA blocked. For a web browser nowadays, as Microsoft has learned, it's better to pretend to be Webkit than to try to convince people to implement 'proper' checking for features.