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

Re: [css-syntax]The emperor isn't naked, but he's wearing his underpants on his head

From: Gérard Talbot <www-style@gtalbot.org>
Date: Sat, 05 Nov 2016 20:01:10 -0400
To: Felix Miata <mrmazda@earthlink.net>
Cc: W3C www-style mailing list <www-style@w3.org>
Message-ID: <b59245dbf3f7995236078796e55a2616@gtalbot.org>
Le 2016-11-05 19:03, Felix Miata a écrit :
> Gérard Talbot composed on 2016-11-05 17:47 (UTC-0400):
>> An inline style is (should be!) for an unique element.
>> Therefore, an inline style should be more specific than a class.
> That only works if the only styles are author, or if users aren't
> supposed to have ultimate control.

Yes. If media (origin) is the same and if importance (user, author, user 
agent with !important or not) is the same, then inline style is more 
specific than a class attribute.


> AFAICT, inline styles are
> hopelessly immune to user overrides,

Hm... no. An author inline style can be (will be and should be) 
overriden by an user !important class attribute. Untangling specificity 
only comes after untangling importance. And I believe the CSS 2.1 test 
suite has not tested this... can not find it in


I think we need to test this... Something like:

         <p id="cascade">PREREQUISITE: The <a 
href="support/cascade.css">"cascade.css"</a> file is enabled as the user 
agent's user style sheet.</p>
         <p>Test passes if "Text sample" is green.</p>
         <h1 class="cascadegreenimportant" style="color: red;">Text 

where the user style sheet is:



> thus shouldn't be in the spec at
> all. Users shouldn't have to disable styles entirely in order to make
> one specific element usable.

I agree. Users shouldn't have to disable author styles entirely in order 
to make one specific element usable.

Received on Sunday, 6 November 2016 00:01:48 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:15:01 UTC