W3C home > Mailing lists > Public > www-style@w3.org > April 2011

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 22 Apr 2011 08:15:09 -0700
Message-ID: <BANLkTi=uT+JDDRw3eRMJo00mHA-QHGZ3Kw@mail.gmail.com>
To: Alexander Shpack <shadowkin@gmail.com>
Cc: www-style <www-style@w3.org>
On Fri, Apr 22, 2011 at 2:06 AM, Alexander Shpack <shadowkin@gmail.com> wrote:
> Using of four (or more) browser specific properties make css file unreadable.
>
> I propose replace this list
>
> something: foo;
> -moz-something: foo;
> -o-something: foo;
> -webkit-something: foo;
> -ms-something: foo;
> ...
>
> by
> something: foo;
> *-something: foo;
>
> UA will use standard if it possible, or specific behavior otherwise.
>
> Or, more flexible property declaration:
>
> *something: foo;
>
> Try standard behavior first, or use specific if it possible.

This has been discussed before.  It suffers from the fact that, when
browsers differ from the standard in their experimental
implementations, they quite commonly differ in slightly incompatible
ways.  Folding them into a single property so that you can't target
each browser with different code means that the prefix is somewhat
unusable.

As has been discussed before, prefix hell serves a very valuable
purpose.  When all four browsers are prefixing a property, though,
that's a strong indication that that particular feature should be
fast-tracked to unprefixed.

~TJ
Received on Friday, 22 April 2011 15:15:56 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:39 GMT