W3C home > Mailing lists > Public > www-style@w3.org > December 2009

Re: [css-style-attr] New Editor's Draft

From: fantasai <fantasai.lists@inkedblade.net>
Date: Fri, 11 Dec 2009 16:15:36 -0800
Message-ID: <4B22E0A8.1060001@inkedblade.net>
To: "L. David Baron" <dbaron@dbaron.org>
CC: Giovanni Campagna <scampa.giovanni@gmail.com>, Brad Kemper <brad.kemper@gmail.com>, www-style@w3.org
L. David Baron wrote:
> On Friday 2009-12-11 12:56 -0800, fantasai wrote:
>> A "style" attribute does not need to be named 'style'. It's possible
>> to have <elem style1="..." style2="..."/> and have the document language
>> define both style1 and style2 as "style" attributes.
>>
>> I can add a sentence saying that if a document language allows this,
>> it must specify in which order the attributes' values are concatenated.
> 
> If a language allows this, they should be separate style rules, not
> string-concatenated and parsed as one style rule.  (This affects
> error handling, comments, etc.)
> 
> However, I think it would also be fine to say that conforming
> document languages cannot allow such a situation.

I've added the following:

   # The CSS Working Group strongly recommends that document languages do
   # not allow multiple style attributes on a single element. If a document
   # language allows multiple style attributes, each is parsed independently
   # and treated as a separate style rule, the ordering of which should be
   # defined by the document language, else is undefined.

It's possible some document language will define a namespaced 'style'
attribute, which can then be included in an HTML element with a local
'style' attribute or something similarly absurd. So I felt it was best
to define /something/.

~fantasai
Received on Saturday, 12 December 2009 00:16:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 03:47:12 GMT