2 ms·

Do they support NaCl and WebRTC and WebGL and WineVine DRM like Chrome, now that they stuff "Chrome" in their User-Agent? If not, what happens if a site (poorly

by 0x0 12y ago

Do they support NaCl and WebRTC and WebGL and WineVine DRM like Chrome, now that they stuff "Chrome" in their User-Agent? If not, what happens if a site (poorly) detects these features from the user agent?

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 ago
  Gee, just look for 'Gecko' in UA strings. That'll catch 'em.
- 0x0 12y ago
  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.
Strom 12y ago
A poorly written site will perform poorly. The hope is that newer sites (and sites using WineVine DRM are newer, relatively speaking) aren't written as poorly as old ones. Well written sites use feature detection, not user-agent detection. This move by Microsoft addresses problems with older sites, and IE12 supports these older features that the site doesn't belive IE can support.
- TazeTSchnitzel 12y ago
  Hah, if only it were "older sites". People do user agent sniffing all the time, unfortunately. Thus the massive IE Mobile user agent string.
- ArtDev 12y ago
  Poorly implemented features means you can't fully use them. Building a website that has to work on Internet Explorer is like teaching. Its like having to teach the class to the dumbest kid in the room. You can't take the dumb kid outside for extra instruction (because that would be browser targeting.. ). Everyone has to wait, until the dumb kid gets it.

by 0x0 12y ago

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 ago
Gee, just look for 'Gecko' in UA strings. That'll catch 'em.
0x0 12y ago
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.

Strom 12y ago

A poorly written site will perform poorly. The hope is that newer sites (and sites using WineVine DRM are newer, relatively speaking) aren't written as poorly as old ones. Well written sites use feature detection, not user-agent detection. This move by Microsoft addresses problems with older sites, and IE12 supports these older features that the site doesn't belive IE can support.

TazeTSchnitzel 12y ago
Hah, if only it were "older sites". People do user agent sniffing all the time, unfortunately. Thus the massive IE Mobile user agent string.
ArtDev 12y ago
Poorly implemented features means you can't fully use them. Building a website that has to work on Internet Explorer is like teaching. Its like having to teach the class to the dumbest kid in the room. You can't take the dumb kid outside for extra instruction (because that would be browser targeting.. ). Everyone has to wait, until the dumb kid gets it.