- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Nov 2023 02:43:14 +0000
- To: public-css-archive@w3.org
khushalsagar has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-view-transitions-1] View Transition on a fragmented inline == We resolved that fragmented elements should be ignored by View Transition here: https://github.com/w3c/csswg-drafts/issues/8339#issuecomment-1470268830. But its not clear whether this resolution also covers inline-box fragmentation across line boxes. The spec is limited to box fragmentation : [If element has more than one box fragment, then continue.](https://drafts.csswg.org/css-view-transitions-1/#changes-since-2022-05-30:~:text=If%20element%20has%20more%20than%20one%20box%20fragment%2C%20then%20continue.). So filing this issue to resolve on the behaviour for inline fragmentation. IIRC we resolved on ignoring box fragmentation because: 1. The position model was very hard to define. If a fragmented box has a transform it individually applies to each fragment. So unioning all the fragments to generate an image and then applying the transform on top of this image (which is how View Transition works) wasn't feasible. 2. There are plans to make each fragment addressable in CSS via pseudo-elements like nth-fragment in which authors can add a view-transition-name to any fragment. 1 is not a concern for inlines because `transform` property doesn't apply there. So we could consider an approach of unioning all line box fragments here. 2 is interesting in that you can already target the first line box via `::first-line`. @fantasai @tabatkins any advice on this? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9567 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 November 2023 02:43:15 UTC