On 19/1/09 02:10, Gunlaug Sørtun wrote: > Vendor-specific CSS properties are for the most part safe to use in that > they don't end up disturbing other browsers - although I have seen that > happen too.
I can imagine implementations of vendor-specific CSS properties changing between versions (but then this also happens with standardized properties). I'd be surprised to find a vendor-specific CSS property (that is, a prefixed vendor-specific CSS property) affecting another web engine and interested as to how that would even happen - it sounds like a parsing bug. Do you have an example of this? > Note that *nothing in CSS gets standardized* until there are at least > two interoperable implementations - at least two browsers must have > pretty identical and flawless support for what's only a suggestion. This > means we have to use the proposed properties/values if we want them to > become recommended parts of standards. Why do you think the two interoperable implementations rule means we need to author mainstream CSS based on guesses about how future implementations will work? That could be bad for the development of CSS, because improving the spec for those features could break web content that relied on those assumptions. Readers may wish to review the introductions to - http://www.w3.org/TR/CSS21/ and http://www.w3.org/TR/css3-mediaqueries/ - for example statements of the two interoperable implementations rule. -- Benjamin Hawkes-Lewis ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
