Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

IE conditional comments to target ie9/ie10 and non-ie browser

See original GitHub issue

Consider adding a conditional comment to target ie9, ie10 and non ie-browser :

<!-- paulirish.com/2008/conditional-stylesheets-vs-css-hacks-answer-neither/ -->
<!--[if lt IE 7]> <html class="no-js lt-ie9 lt-ie8 lt-ie7" lang="en"> <![endif]-->
<!--[if IE 7]>    <html class="no-js lt-ie9 lt-ie8" lang="en"> <![endif]-->
<!--[if IE 8]>    <html class="no-js lt-ie9" lang="en"> <![endif]-->
<!--[if IE 9]>    <html class="no-js lt-ie10" lang="en"> <![endif]-->
<!-- Consider adding a manifest.appcache: h5bp.com/d/Offline -->
<!--[if gt IE 9]><!--> <html class="no-js gt-ie9 non-ie" lang="en"> <!--<![endif]-->

This allows to differentiate ie9 from browsers that offer a better support of html5/css3 (ie10, chrome, FF, safari) and to write rules that should never be applied when the browser is Internet Explorer.

I just needed that on site’s form for graceful degradation of the placeholder attribute without using any javascript. This allows to hide form labels and use placeholder where supported (ie10, chrome, FF, saf.) and to show labels where placeholders are not supported (ie9 and below).

Issue Analytics

State:
Created 12 years ago
Comments:10 (1 by maintainers)

Top GitHub Comments

1reaction

thisispvbcommented, Feb 28, 2012

We already had this, but it has been removed in #142 because IE9 is not so bad compared to it’s predecessors.

0reactions

Johnny5kcommented, Nov 14, 2012

Since IE10 doesn’t recognize any conditional comments, <!–[if gt IE 9]> actually means the same thing to it as <!–[if !IE]>. So shouldn’t it be changed to <!–[if !IE]> now that we know that? Or will that confuse developers who think that means (logically) that it’s not going to target IE10? So it’s either support the correct way that’s confusing, or continue to support the old way that’s more logically correct, but is actually meaningless…

Leave it to Microsoft to make a statement as simple as [if !IE] not exclude all versions of IE. (I get why they’re getting rid of conditional comments; it’s just going to be a weird transitional period – and I can’t imagine there won’t be SOMETHING we’ll still need to detect IE10 for)