Re: [css3-selectors] Proposal for browser specific prefix

Alexander Shpack:

> Using of four (or more) browser specific properties make css file unreadable.

So don’t do it.

FWIW, I agree that working draft properties and values should be supported (additionally) in all browsers with an W3C prefix ( ‘-w3c-’ or ‘-css-’ and ‘-svg-’) and only proprietary (internal or proposed) ones should use vendor prefixes (‘-moz-’, ‘-o-’, ‘-webkit-’, ‘-ms-’, ‘-ah-’, ‘-prince-’, …) or 3rd party spec prefixes (‘-epub-’, ‘-wap-’, …).

Please also see work in progress resume of previous discussions: <http://wiki.csswg.org/spec/vendor-prefixes>.

Received on Friday, 29 April 2011 10:14:00 UTC