3 ms·
While it can be confusing, that by itself should not be an issue for anyone, they did it to avoid all the older IE specific fix as they become compliant with a
by nolok 13y ago
While it can be confusing, that by itself should not be an issue for anyone, they did it to avoid all the older IE specific fix as they become compliant with a more recent set of standards, and any website should use feature detection rather than browser detection.
- shmichael 13y agofeature detection happens too late, if you want to serve fast.
- shmichael 13y agofeature detection happens too late, if you want to serve fast.
- shmichael 13y agofeature detection happens too late, if you want to serve fast.
- randomfool 13y agoI could have sworn that some compat modes fairly faithfully mimic the original version- to the point of dropping APIs such as addEventListener. So yes, you can use feature detection but if you get flagged by IE then you essentially need to code for IE7 or whatever.
- nilliams 13y agoThe feature detection mantra is true for you and me, but it's a leap to say you can apply the same tactic to a huge site like Google. Google isn't stupid, if they UA sniff, you can bet they have good reasons.
- gcb1 13y agobs. most fixes for ie are implemented with the conditional comment, maybe even one for each version of ie. loading a truckload of css. and honestly, for most cases feature detection is just an empty term. i agree with if t for javascript. but the rest is mostly impossible (or so much more work that it is i practical)