- From: Gérard Talbot <css21testsuite@gtalbot.org>
- Date: Mon, 11 Apr 2011 08:56:31 -0700
- To: "Řyvind Stenhaug" <oyvinds@opera.com>
- Cc: "Public CSS test suite mailing list" <public-css-testsuite@w3.org>, "fantasai" <fantasai.lists@inkedblade.net>
Le Lun 11 avril 2011 7:19, Ă˜yvind Stenhaug a écrit :
> On Sat, 09 Apr 2011 22:28:09 +0200, GĂ©rard Talbot
> <css21testsuite@gtalbot.org> wrote:
>
>> "
>> A value of 'none' within the 'list-style' property sets whichever of
>> 'list-style-type' and 'list-style-image' are not otherwise specified
>> to
>> 'none'.
>> "
>> http://www.w3.org/TR/CSS21/generate.html#propdef-list-style
>>
>>
>> line 31: .three { list-style: none square; }
>>
>> So, it seems that such 'none' should then also set 'list-style-type'
>> sub-property to 'none'.
>
> No, the "square" part is what the spec is trying to refer to as
> "otherwise
> specified".
Řyvind,
I understand your interpretation.
I am very much convinced that such ("... whichever ... not otherwise
specified ...") sentence in the spec should be improved to reduce risks
of confusion, sources of multiple interpretations. Maybe break that
sentence in 2. Providing one carefully built example would probably
suffice.
ul {list-style: none square;}
'list-style-image' is initially set to 'none': so the ("... whichever
... not otherwise specified ...") sentence in the spec does not have to
apply to begin with.
On the other hand,
ul {list-style: url("ellipse.png") none;}
only sets 'list-style-type' to 'none'.
Syntaxically speaking, the ("... whichever ... not otherwise specified
...") sentence of the spec is not easy to interpret.
Gérard
--
Contributions to the CSS 2.1 test suite:
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/
CSS 2.1 Test suite RC6, March 23rd 2011
http://test.csswg.org/suites/css2.1/20110323/html4/toc.html
CSS 2.1 test suite contributors:
http://test.csswg.org/source/contributors/
Received on Monday, 11 April 2011 15:57:03 UTC