W3C home > Mailing lists > Public > public-webplatform@w3.org > December 2012

Re: Tying CSSOM and CSS

From: Chris Mills <cmills@opera.com>
Date: Wed, 5 Dec 2012 09:51:03 +0000
Cc: Alex Komoroske <komoroske@google.com>, public-webplatform@w3.org
Message-Id: <8233FE79-1327-4304-8B24-B9638704C7EB@opera.com>
To: PhistucK <phistuck@gmail.com>
On 5 Dec 2012, at 09:01, PhistucK <phistuck@gmail.com> wrote:

> Every CSS property has its CSSOM counterpart.
> For example, float has cssFloat, font-weight has fontWeight.
> 
> As far as I know, both of them share the same values.
> Therefor, we should make one draw from the other (CSSOM would draw from CSS). If values are added or removed from the CSS property, the CSSOM property should also be updated automatically.
> 

This sounds like a great idea that would save a lot of time in the long run, if it were possible. What's another template between friends? ;-)

> I guess we could do that by adding a field to the CSS property form, that holds its CSSOM counterpart name.
> Can we populate it automatically according to the naming convention? can we take the CSS property name (API_name, I guess) and automatically convert it camelCase by default? Of course, the field should still be editable in case some properties do not use this exact convention (cssFloat, MozColumns)?
> 
> Maybe the summary/overview or other sections should also be drawn. Examples should not be drawn.
> 
> Another idea -
> Completely remove the CSSOM property pages and make them redirect to the CSS property page.
> (I am not in favor of this idea.)
> 
> 
> ☆PhistucK
> 
Received on Wednesday, 5 December 2012 09:52:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:57:36 UTC