[csswg-drafts] [css-view-transitions-1][cssom] Clarify how `getComputedStyle` should be have with view-transition pseudo-elements (#9880)

noamr has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-view-transitions-1][cssom] Clarify how `getComputedStyle` should be have with view-transition pseudo-elements ==
The current specified behavior in CSSOM re pseudo-elements is a bit vague: 

f pseudoElt is provided, is not the empty string, and starts with a colon, then:
[Parse](https://drafts.csswg.org/css-syntax-3/#css-parse-something-according-to-a-css-grammar) pseudoElt as a [<pseudo-element-selector>](https://drafts.csswg.org/selectors-4/#typedef-pseudo-element-selector), and let type be the result.
If type is failure, or is an [::slotted()](https://drafts.csswg.org/css-scoping-1/#selectordef-slotted) or [::part()](https://drafts.csswg.org/css-shadow-parts-1/#selectordef-part) pseudo-element, let obj be null.
Otherwise let obj be the given pseudo-element of elt.

We should clarify what this mean for view-transition pseudo-elements?
- what happens when there is no active transition
- what happens with wildcards/classes

Current chromium implementation gives an actual value for pseudos with names but no *, and regardless of whether the transition is active. This seems a bit coincidental.


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9880 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 30 January 2024 16:57:18 UTC