- From: Etan Wexler <ewexler@stickdog.com>
- Date: Thu, 14 Nov 2002 07:01:20 -0500
- To: www-style@w3.org, Bert Bos <bert@w3.org>, Tantek Çelik <tantekc@microsoft.com>, Ian Hickson <ian@hixie.ch>, Håkon Wium Lie <howcome@opera.com>
Following are substantive comments on section 12, "Generated content and lists" (<http://www.w3.org/TR/2002/WD-CSS21-20020802/generate.html>), of the Cascading Style Sheets level 2.1 draft (<http://www.w3.org/TR/2002/WD-CSS21-20020802>). 12.1 The :before and :after pseudo-elements "User agents must ignore the following properties with :before and :after pseudo-elements: 'position', 'float', list properties, and table properties." Why are 'position' and 'float' to be ignored? How is positioning and floating generated content more burdensome than positioning and floating child elements? 12.2 The 'content' property "Value:" ... "attr(X)" Change "X" to "<identifier>". According to the rules of the "Value" field, "X" is a keyword and must be read literally. 12.3 Interaction of :before and :after with 'run-in' elements "this source document: <h3>Centaurs</h3> <p>have hoofs <p>have a tail" The example document is neither well-formed XML nor valid HTML. I suggest the following XML document instead. <doc> <heading>Centaurs</heading> <para>have hoofs</para> <para>have a tail</para> </doc> 12.5.1 Lists: the 'list-style-type', 'list-style-image', 'list-style-position', and 'list-style' properties "A URI value may be combined with any other value" Change to "A URI may be just one of several terms in a value"
Received on Thursday, 14 November 2002 07:12:37 UTC