W3C home > Mailing lists > Public > www-style@w3.org > March 2016

Re: [css-extensions] rename to prevent confusion with proprietary extensions

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 31 Mar 2016 10:22:11 -0700
Message-ID: <CAAWBYDAH8bo0oDytTA-=43d__dVYmPZj=jqfZc+Q+pnpx1Dzrg@mail.gmail.com>
To: Nick Levinson <nick_levinson@yahoo.com>
Cc: www-style list <www-style@w3.org>
On Sat, Mar 19, 2016 at 12:17 PM, Nick Levinson <nick_levinson@yahoo.com> wrote:
> Please rename CSS Extensions to something else. I hesitate to propose this, since once someone adopts a name it's highly unlikely it will ever be changed except through merger or equivalent. But the term "CSS extensions" is in much wider use to refer to something else entirely, namely, branded CSS properties proprietarily implemented before W3C adapts them (e.g., -moz-* or -webkit-*). The duality of meaning makes searching in Google for discussions of the CSS Extensions specification (a spec for making stylesheets more concise by assigning shared terminology) much more cumbersome and less likely to be fruitfully pursued by developers. An example of the problem was when I searched in caniuse.com for any use of your spec, but it doesn't report on it (I have requested that they add such reports).
>
> Perhaps the spec can be renamed to CSS Concision.

This is a reasonable request!  I'll say, tho, that I hate "CSS
Concision" really bad. ^_^

How about "CSS Custom Extensions", with shortname "css-custom"?

~TJ
Received on Thursday, 31 March 2016 17:22:59 UTC

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