W3C home > Mailing lists > Public > www-style@w3.org > January 2012

Re: [css3-*] Review of functional syntax in CSS

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 20 Jan 2012 11:18:06 -0800
Message-ID: <CAAWBYDAqhc=9YNkPs2T-XN-nr6Tzk+cVcXEo+bmT5MV5JqiDTg@mail.gmail.com>
To: Matthew Wilcox <elvendil@gmail.com>
Cc: Aryeh Gregor <ayg@aryeh.name>, Henri Sivonen <hsivonen@iki.fi>, www-style list <www-style@w3.org>
On Fri, Jan 20, 2012 at 11:09 AM, Matthew Wilcox <elvendil@gmail.com> wrote:
> I am all for making CSS syntax as similar to JS as possible - as the CSS features become more powerful and complex to express it simply makes sense to borrow the syntax from a more powerful sibling web technology.
> As for the prefix pattern whereby authors are dropping a no-prefix property at the end of the list: I'm guilty of it whenever I use any prefixed property. The idea is to be forward compatible otherwise when a spec goes final and vendors remove support for the prefixed version website's *appear* to break.
> Arguably that's an author's problem for using incomplete properties in production environments instead of for personal projects - but that's what happens because it's the fancy new stuff which sells and make's client's happy, so it's the fancy new stuff that get's used as soon as it's practical to do so.
> I'd suggest that the only way to avoid this kind of problem is to get browser vendors to disable all experimental vendor-specific prefixes unless the user has opted in through a preference or special build. The problem there is it's not in the vendor's interest to do this because it is the fact that Safari and Chrome can do fancy stuff that pushes their share of the market up. It's certainly one reason I like Chrome/Safari - I love those hardware accelerated 3D Transforms, they make clients drool and developers lust.

We have other threads for talking about what precisely the "prefix
problem" is and how to solve it.  Let's not get into it here.  ^_^

Received on Friday, 20 January 2012 19:18:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:10 UTC