[csswg-drafts] [css-lists][css-display] The two specs may disagree on whether element with "display: contents" should create counter scope

upsuper has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== [css-lists][css-display] The two specs may disagree on whether 
element with "display: contents" should create counter scope ==
CSS Lists and Counters spec 
[says](https://drafts.csswg.org/css-lists-3/#counters-without-boxes):
> An element that does not generate a box ... cannot set, reset, or 
increment a counter. The counter properties are still valid on such an
 element, but they must have no effect.

While there is an issue listed in CSS Display spec 
[says](https://drafts.csswg.org/css-display-3/#valdef-display-contents):
> **ISSUE 1** `contents` currently only has an effect on box 
generation and layout. Other things that care about the document tree 
are unaffected, like counter scopes. Is this what we want?

I'm not sure if there is any normative text in CSS Display spec leads 
to that issue, but given that the issue exists, there might be some 
disagreement between the two specs we may want to resolve.

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/674 using your GitHub 
account

Received on Thursday, 3 November 2016 04:43:25 UTC