- From: Steve Kobes (Chromium) via GitHub <noreply@w3.org>
- Date: Tue, 20 Jan 2026 16:30:54 +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] ::v-t-old and ::v-t-new should be display:block == In the [global view transition user agent style sheet](https://drafts.csswg.org/css-view-transitions-2/#ua-styles), the `::view-transition-old` and `::view-transition-new` elements are `position: absolute` without an explicit `display` or `inset-inline-start`. Setting `position: absolute` causes the computed style of `display` to be `block`, but the resolution of `inset-inline-start: auto` uses the static offset determined as if the element had its initial `display` value, which is `inline` ([illustration](https://output.jsbin.com/gamoxak)). This can cause problems such as inappropriate horizontal shifting if an ancestor has `text-align: center` ([crbug.com/476120655](https://crbug.com/476120655)). It would be better for the UA style sheet to explicitly set either `display: block` or `inset-inline-start: 0` (or both). cc @vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13373 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 January 2026 16:30:55 UTC