- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Apr 2025 15:17:37 +0000
- To: public-css-archive@w3.org
emilio has just created a new issue for https://github.com/w3c/csswg-drafts:
== [css-view-transitions-1] What's the point of position: fixed in `::view-transition`? ==
https://drafts.csswg.org/css-view-transitions-1/#snapshot-containing-block-concept says:
> The [snapshot containing block](https://drafts.csswg.org/css-view-transitions-1/#snapshot-containing-block) is considered to be an [absolute positioning containing block](https://drafts.csswg.org/css-position-3/#absolute-positioning-containing-block) and a [fixed positioning containing block](https://drafts.csswg.org/css-position-3/#fixed-positioning-containing-block) for [::view-transition](https://drafts.csswg.org/css-view-transitions-1/#selectordef-view-transition) and its descendants.
Then https://drafts.csswg.org/css-view-transitions-1/#ua-styles:
```css
:root::view-transition {
position: fixed;
inset: 0;
}
```
but afaict that `position: fixed` is just confusing, and behaving exactly the same as `position: absolute`, since the snapshot CB is a `position: fixed` containing block, right?
Should we change it just for clarity? Is it just an historical artifact?
cc @noamr @BorisChiou @vmpstr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12116 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 April 2025 15:17:38 UTC