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

Re: [cssom] Supporting JS properties whose names are CSS property names on CSSDeclaration objects

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 15 Feb 2012 16:29:42 -0800
Message-ID: <CAAWBYDCV9Dc_8RjnSihhOAdnDbg_uPgeyKECgiH4t6YhXPZ6RA@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, Glenn Adams <glenn@skynav.com>, www-style list <www-style@w3.org>
On Wed, Feb 15, 2012 at 4:25 PM, L. David Baron <dbaron@dbaron.org> wrote:
> On Wednesday 2012-02-15 15:41 -0800, Tab Atkins Jr. wrote:
>> On Wed, Feb 15, 2012 at 3:03 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> > On 2/15/12 6:00 PM, Tab Atkins Jr. wrote:
>> >> The appropriate algorithm is already defines in HTML, and can be
>> >> copied for the CSSOM (it's used to convert between data-* attributes
>> >> and properties on the dataset object).
>> >
>> > Except for the float/cssFloat thing, right?
>> Yup.  (And as far as I can tell, that's the only exception, right?)
> Yes, based on what Gecko implements.  (Though I didn't check that
> the dash-to-case conversion was correct; I just removed all the
> dashes and lowercased everything, and then float/cssFloat was the
> only case where there was a difference between what's on
> CSS2Properties and the name of the CSS property.)
> (I think there are some similar things in the HTML DOM somewhere,
> though.)

Yes, @class is reflected as 'className' in the DOM, and there may be
another exception floating around somewhere.

Received on Thursday, 16 February 2012 00:30:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:55 UTC