- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Nov 2022 09:27:36 +0000
- To: public-css-archive@w3.org
Here are the options I see: ## Option 1: Use DOM's append etc definitions I don't think this is a good idea, because those algorithms are not designed for pseudo-elements. Anyone following that definition will make incorrect assumptions or be confused. ## Option 2: Leave it as a hand-wave & file an issue with the pseudo-element spec Just use "append", "remove", and "descendant pseudos" as unlinked term, with an `Issue:` pointing to a GitHub issue for the pseudo-element spec to define them. ## Option 3: Add a stub spec for pseudo-children to the VT spec, with an issue noting it should be moved to the pseudo-element spec This is what https://github.com/w3c/csswg-drafts/pull/8126 currently does (except the issue noting it should be moved, but I'll add that). This would also give us somewhere to specify `:only-child`. --- I kinda like the pattern of option 3, "spec locally in a way that works locally. Then aim to move it into a more general spec". But I'm ok with option 2 too. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8113#issuecomment-1326178407 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 November 2022 09:27:38 UTC