- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Jun 2019 17:10:12 +0000
- To: public-css-archive@w3.org
@dbaron Currently, if you view both: 1. http://jsfiddle.net/5rcjk9gv/3 2. http://jsfiddle.net/5rcjk9gv/4 Their only difference is css line 5, changing the `counter-increment` from targeting an element that has no box, because of `display:contents`, to an element that is the descendant of an element that has no box. The first case is consistent and seems desirable across vendors. The second case only seems desirable in gecko/blink. In gecko/blink, sharing the incrementing through the `display:content` "layer" has allowed me better semantics and more portable/component styling. In webkit, the second case doesn't allow the same shared incrementing through the `display:content` ancestor, only incrementing once for each inner most element that outputs the counter. Case 2 - Gecko/Blink <img width="607" alt="Screen-Shot-2019-06-05-at-1 02 37-PM" src="https://user-images.githubusercontent.com/181364/58975086-b943ac00-8789-11e9-89e9-54b838e0cc3b.png"> Case 2 - Webkit <img width="607" alt="Screen Shot 2019-06-05 at 1 02 19 PM" src="https://user-images.githubusercontent.com/181364/58975096-bf398d00-8789-11e9-9331-1efc1094f256.png"> For all I really know, what I'm asking about is supported by the current box tree defined state of the spec, but I just haven't understood the answers to me question yet related to the cases I've linked here for the third time. :/ -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/674#issuecomment-499172746 using your GitHub account
Received on Wednesday, 5 June 2019 17:10:14 UTC