[cssom] Should getComputedStyle() support non-standard pseudo-elements?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
https://drafts.csswg.org/cssom/#dom-window-getcomputedstyle
See https://github.com/w3c/csswg-drafts/pull/3968#issuecomment-496033399
Why does getComputedStyle() support any pseudo-element? Previously it only supported ::before and ::after.
This is an issue for appearance because UAs can support non-standard values for non-standard pseudo-elements. (Though css-ui could require auto to be used instead.)
Do we want such pseudo-elements to be available in author CSS? Do we want to support them in getComputedStyle()?
cc @frivoal @fantasai @FremyCompany
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the CSSOM getComputedStyle() definition and the CSSWG pull request 3968 comment linked in the issue. Resolve whether non-standard pseudo-elements should be exposed to author CSS and supported by getComputedStyle(), including the appearance/auto question; done means the specification's intended behavior is decided and reflected in the relevant draft.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100