- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Mar 2023 11:24:08 +0000
- To: public-css-archive@w3.org
> The Firefox implementation doesn't seem to align to the [spec](https://w3c.github.io/csswg-drafts/css-images-4/#element-notation:~:text=If%20the%20referenced%20element%20has%20a%20transform%20applied%20to%20it%20or%20an%20ancestor%2C%20the%20transform%20must%20be%20ignored%20when%20rendering%20the%20element%20as%20an%20image.), it explicitly states that transforms on the element should be ignored: "If the referenced element has a transform applied to it or an ancestor, the transform must be ignored when rendering the element as an image." > > View Transition [spec](https://drafts.csswg.org/css-view-transitions-1/#capture-rendering-characteristics:~:text=If%20the%20referenced%20element%20has%20a%20transform%20applied%20to%20it%20(or%20its%20ancestors)%2C%20then%20the%20transform%20is%20ignored) handles transforms the same way, they are ignored when rendering the element's image: "If the referenced element has a transform applied to it (or its ancestors), then the transform is ignored". I'm not convinced these are the same. With view transitions we apply ancestor transforms, and capture the target transform. The `element()` spec is vague, but I'm not sure "the transform must be ignored" is the same thing. The `element()` spec does have specific things to say about fragmentation: > If the referenced element is broken across pages, the element is displayed as if the page content areas were joined flush in the pagination direction, with pages' edges corresponding to the initial containing block’s start edge aligned. Elements broken across lines or columns are just rendered with their [decorated bounding box](https://w3c.github.io/csswg-drafts/css-images-4/#decorated-bounding-box). I'm not 100% sure what this means, particularly in the multi-column layouts where the column widths are not equal (which [seems to be possible using negative margins](https://stackoverflow.com/a/29156418/123395), although that might be an implementation bug). -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8339#issuecomment-1469828484 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 March 2023 11:24:14 UTC