Some browser specific CSS hacks: Difference between revisions

The educational technology and digital learning wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Here you can find some examples of browser specific hacks. It is best to refrain from the use of hacks when possible, since they are considered to be bad practice and will often keep CSS code from validating. For more detailed information on hacks and other solutions to browser inconsistencies, visit the [http://edutechwiki.unige.ch/en/CSS_compatibility CSS compatibility] page on this wiki. You can also access the original post that listed the information below via this [http://paulirish.com/2009/browser-specific-css-hacks/ link].
Here you can find some examples of browser specific hacks. It is best to refrain from the use of hacks when possible, since they are considered to be bad practice and will often keep CSS code from validating. For more detailed information on hacks and other solutions to browser inconsistencies, visit the [[CSS compatibility]] page on this wiki. You can also access the original post that listed the information below via this [http://paulirish.com/2009/browser-specific-css-hacks/ link].


<pre>
<pre>
Line 76: Line 76:
#veintesiete { color: blue !ie; } /* string after ! can be anything */
#veintesiete { color: blue !ie; } /* string after ! can be anything */
</pre>
</pre>
[http://paulirish.com/2009/browser-specific-css-hacks/ Here is the reference to the original post.]
[http://paulirish.com/2009/browser-specific-css-hacks/ Here is the reference to the original post.]
[http://edutechwiki.unige.ch/en/CSS_compatibility Go back to CSS compatibility page]
 
[[CSS_compatibility|Go back to CSS compatibility page]]
 
[[Category:CSS]]

Latest revision as of 15:23, 12 December 2011

Here you can find some examples of browser specific hacks. It is best to refrain from the use of hacks when possible, since they are considered to be bad practice and will often keep CSS code from validating. For more detailed information on hacks and other solutions to browser inconsistencies, visit the CSS compatibility page on this wiki. You can also access the original post that listed the information below via this link.

/***** Selector Hacks ******/

/* IE6 and below */
* html #uno  { color: red }

/* IE7 */
*:first-child+html #dos { color: red } 

/* IE7, FF, Saf, Opera  */
html>body #tres { color: red }

/* IE8, FF, Saf, Opera (Everything but IE 6,7) */
html>/**/body #cuatro { color: red }

/* Opera 9.27 and below, safari 2 */
html:first-child #cinco { color: red }

/* Safari 2-3 */
html[xmlns*=""] body:last-child #seis { color: red }

/* safari 3+, chrome 1+, opera9+, ff 3.5+ */
body:nth-of-type(1) #siete { color: red }

/* safari 3+, chrome 1+, opera9+, ff 3.5+ */
body:first-of-type #ocho {  color: red }

/* saf3+, chrome1+ */
@media screen and (-webkit-min-device-pixel-ratio:0) {
 #diez  { color: red  }
}

/* iPhone / mobile webkit */
@media screen and (max-device-width: 480px) {
 #veintiseis { color: red  }
}

/* Safari 2 - 3.1 */
html[xmlns*=""]:root #trece  { color: red  }

/* Safari 2 - 3.1, Opera 9.25 */
*|html[xmlns*=""] #catorce { color: red  }

/* Everything but IE6-8 */
:root *> #quince { color: red  }

/* IE7 */
*+html #dieciocho {  color: red }

/* Firefox only. 1+ */
#veinticuatro,  x:-moz-any-link  { color: red }

/* Firefox 3.0+ */
#veinticinco,  x:-moz-any-link, x:default  { color: red  }

/***** Attribute Hacks ******/

/* IE6 */
#once { _color: blue }

/* IE6, IE7 */
#doce { *color: blue; /* or #color: blue */ }

/* Everything but IE6 */
#diecisiete { color/**/: blue }

/* IE6, IE7, IE8 */
#diecinueve { color: blue\9; }

/* IE7, IE8 */
#veinte { color/*\**/: blue\9; }

/* IE6, IE7 -- acts as an !important */
#veintesiete { color: blue !ie; } /* string after ! can be anything */

Here is the reference to the original post.

Go back to CSS compatibility page