News for hackers. Stuff that matters.

A comment on User-agent string changes. Parent comment

Re:User-agent string changes by TazeTSchnitzel on Saturday November 22, 2014 @10:57AM (#8645793)
Why on earth would you detect those things server-side, given you can do the fallback client-side?

Also, no, they don't have those things, aside from WebGL and some form of DRM (not sure if it's the same as Chrome's). The reason they put Chrome in is for sites assuming only Chrome supports web standards (ugh).

[ Parent | on HN ]
Re:User-agent string changes by 0x0 on Saturday November 22, 2014 @11:03AM (#8645812)
It could easily happen client-side, with something like /Chrome/.test(navigator.userAgent).

I mean, there's probably sites using code like this already, why else would IE implement such a user-agent? But then they can't really know which Chrome feature the code is looking for.

I guess they are moving from being unfairly excluded from modern standards, to possibly overshooting their target and getting served experimental features they don't support.

[ Parent | on HN ]
Re:User-agent string changes by Svip on Saturday November 22, 2014 @11:01AM (#8645808)
Gee, just look for 'Gecko' in UA strings. That'll catch 'em.
[ Parent | on HN ]