3 ms·
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
by TazeTSchnitzel 12y ago
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).
- Svip 12y agoGee, just look for 'Gecko' in UA strings. That'll catch 'em.
- 0x0 12y agoIt 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.