On 8 Feb 2007, at 19:15:07, Paul Bennett wrote:
Hi all,
I just noticed via Roger Johansson's blog[1] that the Safari team
are building in non-standard CSS properties[2]. I know this is
nothing new, as Firefox / Mozilla has it's non-standard CSS
commands too (mainly for XUL development?)[3] etc, but wonder what
the motivation is. Isn't this the 2007 equivalent of the <blink>
and <marquee> tags we all know and hate?
What advantage does it give to browser vendors to implement non-
standard CSS properties?
These are usually properties specified in the as-yet-incomplete CSS
3. By implementing them now they allow users to test them and, if CSS
3 is ever completed, can immediately enable them using the standard
name.
Also, note that a W3C Draft can only become a Recommendation
(synonymous with standard) if there are working, interoperable real-
world implementations from more than one vendor; so once the CSS
Working Group finally end their deliberations over CSS 3, having
these implementations out there can greatly speed up the process of
moving from Candidate Recommendation to Recommendation status.
So it's actually pretty much the opposite of <blink> and suchlike:
it's a way of helping the community prepare for future standards, and
of ensuring that implementations are available at the time the
standard is ratified.
Regards,
Nick.
--
Nick Fitzsimons
http://www.nickfitz.co.uk/
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
