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

Allow using WA-API for nested pseudo elements #163

Closed
khushalsagar opened this issue Jun 27, 2022 · 2 comments
Closed

Allow using WA-API for nested pseudo elements #163

khushalsagar opened this issue Jun 27, 2022 · 2 comments

Comments

@khushalsagar
Copy link
Collaborator

khushalsagar commented Jun 27, 2022

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.

@jakearchibald @vmpstr

@khushalsagar
Copy link
Collaborator Author

Resolved in the external issue.

@jakearchibald
Copy link
Collaborator

External issue: w3c/csswg-drafts#7469

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

No branches or pull requests

2 participants