4 ms·
And even terminating the browser itself doesn't solve the problem. There's still the accursed compatibility mode. We still have to support IE7 and IE8 because o
by CWuestefeld 8y ago
And even terminating the browser itself doesn't solve the problem. There's still the accursed compatibility mode. We still have to support IE7 and IE8 because of this (it looks ugly, but is still functional).
- dspillett 8y ago> the accursed compatibility mode Ah yes, the fun of an almost-impossible-to-reliably-detect setting that affects your display and sometimes worse.
- emergie 8y ago> almost-impossible-to-reliably-detect have you ever tried document.documentMode?
- dspillett 8y agoI thought that was only in IE11, but apparently it has been around since IE8. It is only available client-side though, and while you can feed it back to the server if relevant there (i.e. server-side rendering which most of the legacy code I'm responsible for does) you'd have to keep doing so in case the mode changes between requests. Also you are forced to add in extra conditionals to your page whether you are working client- or server- side: you can respond to this property to deal with display differences via CSS selectors.