- From: Steve Kobes (Chromium) via GitHub <noreply@w3.org>
- Date: Wed, 11 Jun 2025 19:51:00 +0000
- To: public-css-archive@w3.org
skobes-chromium has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-view-transitions-2] [scoped] What is the paint order of the ::v-t pseudo in relation to the scope? == This issue tracks an open question about the behavior of [Scoped View Transitions](https://github.com/WICG/view-transitions/blob/main/scoped-transitions.md). Further context appears in the document [Self-Participating Scopes](https://bit.ly/svt-sps). **Q: What is the paint order of the ::v-t pseudo in relation to the scope?** A child of the scope would normally be stacked with other children according to its `z-index`, but the `::view-transition` pseudo-element should probably be handled specially so that it sits on top of everything in the scope. This is not what Chromium currently does ([crbug.com/421927605](https://crbug.com/421927605)). (Because participants have their render output redirected, this question only matters for children that are _not_ participants and whose `z-index` is larger than that of the `::view-transition`.) cc @noamr @vmpstr @flackr @bramus @jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12325 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 June 2025 19:51:01 UTC