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
Currently pseudo elements created for a transition use the documentElement as the originating element. This allows them to be targeted easily in both css and script APIs (like WA-API and getComputedStyle). We plan to switch this to have each pseudo element originate from its immediate ancestor element in the DOM tree. This requires a change both to target them in CSS and in the script API.
An open issue addresses the gap to make it easier to target them with CSS. Filing this issue to follow up with a change in the script API once the CSS issue is resolved. The long term plan is to use CSSPseudoElement to make script access of these elements similar to DOM elements. In the short term we can add a pseudoSelector (similar to pseudoElement) which allows using a selector to target nested pseudo elements.
Currently pseudo elements created for a transition use the documentElement as the originating element. This allows them to be targeted easily in both css and script APIs (like WA-API and getComputedStyle). We plan to switch this to have each pseudo element originate from its immediate ancestor element in the DOM tree. This requires a change both to target them in CSS and in the script API.
An open issue addresses the gap to make it easier to target them with CSS. Filing this issue to follow up with a change in the script API once the CSS issue is resolved. The long term plan is to use CSSPseudoElement to make script access of these elements similar to DOM elements. In the short term we can add a
pseudoSelector
(similar topseudoElement
) which allows using a selector to target nested pseudo elements.@jakearchibald @vmpstr
The text was updated successfully, but these errors were encountered: