Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[selectors] ::shadow no longer exists? #7474

Closed
Loirooriol opened this issue Jul 7, 2022 · 5 comments
Closed

[selectors] ::shadow no longer exists? #7474

Loirooriol opened this issue Jul 7, 2022 · 5 comments

Comments

@Loirooriol
Copy link
Contributor

https://drafts.csswg.org/selectors-4/#pseudo-element-structure references a ::shadow pseudo-element, defined in https://www.w3.org/TR/css-scoping-1/#selectordef-shadow

But that's an old working draft from 2014. I don't see ::shadow in the editor's draft https://drafts.csswg.org/css-scoping-1/

So this section may need to be changed.

@fantasai
Copy link
Collaborator

fantasai commented Nov 7, 2022

@Loirooriol Fixed by switching to ::slotted. Incidentally, the next example in the section... do you think there's something reasonable we could switch it to, or should I just comment it out?

@Loirooriol
Copy link
Contributor Author

So, ::slotted() is an alias for other elements in the tree, and then I guess it makes sense to have internal structure.

But I don't see https://drafts.csswg.org/css-scoping/#slotted-pseudo saying that it has internal structure.

Also, example 8 is still saying mentioning ::shadow:

the selectors div > span and div::shadow ::slotted > span

Also, AFAIK ::slotted is not valid, it should be ::slotted(*) or something.

@fantasai
Copy link
Collaborator

fantasai commented Nov 8, 2022

@Loirooriol Yeah, I realized that ::slotted doesn't currently have internal structure... that's under discussion somewhere I think. So I switched it to be a hypothetical pseudo-element that doesn't exist, since we don't have any examples yet.

But still, that second example, which relies on both ::slotted and ::shadow existing, do I just comment it out or is there some valid useful thing you think we could replace it with?

@Loirooriol
Copy link
Contributor Author

If right now there is no pseudo-element with internal structure, then I would comment it out.

@Loirooriol
Copy link
Contributor Author

Maybe even comment out the whole section?

jakearchibald pushed a commit to jakearchibald/csswg-drafts that referenced this issue Jan 16, 2023
jakearchibald pushed a commit to jakearchibald/csswg-drafts that referenced this issue Jan 16, 2023
jakearchibald pushed a commit to jakearchibald/csswg-drafts that referenced this issue Jan 16, 2023
jakearchibald pushed a commit to jakearchibald/csswg-drafts that referenced this issue Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants