- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Apr 2025 19:56:33 +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] A lot of the definitions should use ink-overflow rather than border box sizes == https://drafts.csswg.org/css-view-transitions-1/#capture-old-state-algorithm and so on have sections like: > Set capture’s [old transform](https://drafts.csswg.org/css-view-transitions-1/#captured-element-old-transform) to a [<transform-function>](https://drafts.csswg.org/css-transforms-2/#typedef-transform-function) that would map element’s [border box](https://drafts.csswg.org/css-box-4/#border-box) from the [snapshot containing block origin](https://drafts.csswg.org/css-view-transitions-1/#snapshot-containing-block-origin) to its current visual position. And so on. But the captures capture shadows and so on, so that seems wrong, it should account for the potentially negative offsets that outlines and shadows create. Tests like https://wpt.live/css/css-view-transitions/new-content-ancestor-clipped.html where an element with a shadow gets captured depend on it to get the correct rendering. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12092 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 April 2025 19:56:33 UTC