- From: David Bokan via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Nov 2023 16:11:46 +0000
- To: public-css-archive@w3.org
Thanks @khushalsagar - one more thing to consider: would it make sense to specify an ordering for the descendant pseudos of `::view-transition`? At least for the [Animation composite order]() case? It currently [states](https://drafts.csswg.org/css-animations-2/#animation-composite-order:~:text=any%20other%20pseudo%2Delements%20not%20mentioned%20specifically%20in%20this%20list%2C%20sorted%20in%20ascending%20order%20by%20the%20Unicode%20codepoints%20that%20make%20up%20each%20selector): > any other pseudo-elements not mentioned specifically in this list, sorted in ascending order by the Unicode codepoints that make up each selector We actually have an explicit paint ordering for the view-transition-names so I think it'd make sense to order `::view-transition-group` based on that rather than lexographically. Similarly for `::view-transition-new` and `::view-transition-old`. -- GitHub Notification of comment by bokand Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9588#issuecomment-1806019131 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 November 2023 16:11:48 UTC