- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Aug 2024 20:40:41 +0000
- To: public-css-archive@w3.org
dbaron has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-pseudo] more clearly define which pseudo-elements are tree-abiding or part-like == css-pseudo-4 [defines](https://drafts.csswg.org/css-pseudo-4/#treelike) the terms "tree-abiding pseudo-element" and (a stricter subset) "part-like pseudo-element". Some pseudo elements fall into these categories. These cause various things to be allowed. In particular, I think the current list is that tree-abiding pseudo-elements are: * allowed to change the results of `getComputedStyle` * allowed after `::slotted()` * support the `content` property and part-like pseudo-elements do all of the above and also: * support any CSS properties except those that say otherwise * can be followed by most pseudo-classes and any pseudo-elements (not yet specified, see #10083) However, there are multiple specifications that define pseudo-elements, some of which define pseudo-elements that probably belong in one of these categories but don't say so, and some of which define pseudo-elements as tree-abiding when they may want the newer part-like definition instead. We should audit all pseudo-elements and make sure that they're defined appropriately. We should probably also get a group resolution on the result of that audit, since the changes in feature support for many of these pseudo-elements are substantive. (The initial introduction of the part-like term defined a bunch of pseudo-elements as part-like, and I think we could probably use a resolution to approve that.) Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10794 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 August 2024 20:40:42 UTC