- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Apr 2023 18:33:59 +0000
- To: public-css-archive@w3.org
Ah, thanks for this ping! My initial thoughts: > Is it a tree-abiding pseudo-element? Yes, in that it's a well-defined box with a definition location, so should accept all the stuff other boxes do. > If it's a tree-abiding pseudo-element, where is it originated? Before ::marker, between ::marker and ::before, between ::before and 1st child, between last child and ::after, after ::after? None of these; it is generated in the top layer, as an independent box with no particular relationship to its originating element. (But it's rendered just below the originating element.) > It accepts random properties, e.g. display: list-item. But then: > Does it really become a list item? No opinion. I'm fine with forcing it to be `display: block` via a UA style rule. > If it becomes a list item, does it increment the implicit list-item counter as usual? If so, it's position in the tree matters. Right, so having this be impossible is probably reasonable. > Do counter properties even work in ::backdrop? The properties are defined as applying to "all elements (includes ::before and ::after pseudo-elements)", but the ::backdrop definition says "no restrictions". I suppose they do, but we will indeed need to define the position in the tree. I propose that they're an isolated context that doesn't see any other counters, and its own counters are also invisible to any other element. > Does it originate a ::marker pseudo-element? If we force it to `display: block`, no. If not, yes. > Should ::backdrop::marker be a valid selector? It should probably be *valid* regardless of the answer to the previous question, but I suspect we'll end up having it not be capable of matching anything since you won't be able to make it a list item. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7845#issuecomment-1494792723 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 3 April 2023 18:34:01 UTC