You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: