- From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Aug 2019 23:51:56 +0000
- To: public-css-archive@w3.org
Well, we have:
"A list item is any element with its display property set to list-item. List items generate ::marker pseudo-elements"
https://drafts.csswg.org/css-lists-3/#list-item
"list-style-type on the originating element defines a marker string "
https://drafts.csswg.org/css-lists-3/#content-property
"`<counter-style>`
Specifies the element’s marker string as the value of the list-item counter represented using the specified `<counter-style>`. "
https://drafts.csswg.org/css-lists-3/#marker-string
So, if the UA sheet contains `ol { list-style-type: decimal; }` then the rendering you suggest is normative, right? (I don't think it's normative to have that rule, but it's informatively defined in the [appendix](https://drafts.csswg.org/css-lists-3/#ua-stylesheet))
Perhaps the spec should say upfront that all examples assumes an UA sheet similar to the one in the appendix? It'd be rather tedious to list complete markup+style for each example, and it would make them less informative since the reader might not know which rules are necessary for the example to work in a web browser and might start adding lot's of redundant styles. (It looks like most examples assumes existing (UA) style on ol/ul/li elements, fwiw.)
--
GitHub Notification of comment by MatsPalmgren
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4168#issuecomment-517497114 using your GitHub account
Received on Thursday, 1 August 2019 23:51:57 UTC