It is better to avoid such hacks, as they depend on the availability of new standards. It is clear that new standards will be increasingly available on other platforms over time. In other words, it is a mistake to assume that this browser is [a specific browser] because it has [some specific CSS function].
Eric Wendelin's answer is good for targeting WebKit browsers. There's also a good way to configure Gecko browsers:
@-moz-document url-prefix() { }
Add to WebKit targeting (thanks to Eric Wendellin):
@media screen and (-webkit-min-device-pixel-ratio:0) { }
Perhaps you can also reliably use the "object recognition" style of CSS hacks in constructions like this to isolate versions, since you have already correctly isolated the engine, and you can more confidently assume that there will be no difference in the characteristics between versions of this engine change over time.
Obviously, the best way to isolate IE and its various versions is to use conditional comments that IE supported for many versions.
eyelidlessness
source share