W3C home > Mailing lists > Public > www-style@w3.org > June 2010

RE: [css21-selectors] Interpretation of attribute selector

From: Belov, Charles <Charles.Belov@sfmta.com>
Date: Tue, 1 Jun 2010 11:49:27 -0700
Message-ID: <E17F75B6E86AE842A57B4534F82D03769C29CF@MTAMAIL.muni.sfgov.org>
To: "www-style list" <www-style@w3.org>
Cc: "Daniel Glazman" <daniel.glazman@disruptive-innovations.com>, "Boris Zbarsky" <bzbarsky@MIT.EDU>
Daniel Glazman wrote on Friday, May 28, 2010 8:03 AM

>Le 28/05/10 05:42, Boris Zbarsky a écrit :

>> Now the issue you're running into is that the value of the style 
>> attribute is normalized in Gecko, so that the value you put in your 
>> source (or pass to setAttribute) and the value returned by 
>> getAttribute aren't necessarily equal. This is generally considered a 
>> bug (albeit a low-priority one, since it's pretty rare for anyone to 
>> actually work with the string form of the style attribute and since 
>> the string form becomes completely meaningless if you touch ..style.something).

>Pretty rare unless your app is an editor... :-(

>This and the fact the CSS parser in Gecko don't preserve somewhere the unrecognized
>style rules and declarations is a major burden on my shoulders for BlueGriffon.

Also, Word 2003 puts such content into its generated filtered HTML, so it really isn't rare.

Charles Belov
SFMTA Webmaster
http://www.sfmta.com/webmaster
Received on Tuesday, 1 June 2010 18:54:23 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:28 GMT