Last active
December 15, 2015 19:10
-
-
Save ramakay/5309765 to your computer and use it in GitHub Desktop.
This question was initially posed to the @IEDevchat team as I wanted to get a browser manufacturer's view. Is there value in organizing CSS that targets vendor prefixes based on capabilities say via Modernizr ? - e.g: .text-shadow throw all vendor prefixes vs throwing all vendor prefixes regardless and let browser ignore? I am assuming the valu…
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/* | |
Following example assumes scss and ability to target parents selectors. | |
Credits : http://goo.gl/ubE2A & http://goo.gl/AQPpY and | |
*/ | |
.mydeclaration { | |
.nocssanimation & { | |
/* old crappy browser */ | |
border: 1px solid #ccc; | |
} | |
.text-shadow.notouch & { | |
/* Potential ability to add not only text shadow , but gradients etc. | |
Limit your Big Shadows to non touch devices but one's that support text shadow. Also assumes there is some common elements with other declarations | |
*/ | |
} | |
} | |
/* With selector inheritance at compile time , the output will be */ | |
.selector 1 { | |
color: Red; | |
} | |
.text-shadow.notouch selector1, .textshadow.notouch selector n { | |
/* Assumes text shadows are common for the site */ | |
text-shadow: 1px 2px; | |
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment