Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

Need to decide on how to handle pseudo-elements #107

Open
cbiesinger opened this issue Jan 16, 2020 · 2 comments
Open

Need to decide on how to handle pseudo-elements #107

cbiesinger opened this issue Jan 16, 2020 · 2 comments

Comments

@cbiesinger
Copy link

With render-subtree now a CSS property, it can be set on things that are not DOM elements. For example, ::before or ::marker and others.

I think most of that will work fine but we need to think through this, especially if we want to not support it on certain pseudo-elements (maybe ::selection), and if we fire activation events, what elements to fire them on for such cases.

@chrishtr
Copy link
Collaborator

Are there any pseudo-elements we do want to support render-subtree on? The whole point is to avoid rendering the subtree, not the current (pseudo-)element.

@cbiesinger
Copy link
Author

Well, some pseudo-elements can have children (::before { content: "foo"; }), but sure, we could just define them all to ignore this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants