3 ms·

This won't actually work in any other engine except for webkit, even if you vendor-prefix the rules. This is because he is using an :after pseudo element on a c

This won't actually work in any other engine except for webkit, even if you vendor-prefix the rules. This is because he is using an :after pseudo element on a checkbox, which shouldn't work and is technically a bug in webkit (according to the specifications, you cannot use :before/:after on replaced elements).

jacobr 14y ago
Oh, didn't notice that. The specification actually does not explicitly prohibit pseudo content on replaced elements. This specification does not fully define the interaction of :before and :after with replaced elements (such as IMG in HTML). This will be defined in more detail in a future specification. http://www.w3.org/TR/2011/REC-CSS2-20110607/generate.html#before-after-content http://www.w3.org/TR/2011/REC-CSS2-20110607/generate.html#be... In my opinion it would be cool if all browsers supported it.