- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Sun, 07 May 2023 13:16:38 +0000
- To: public-css-archive@w3.org
Sorry but I'm missing how this resolution would work in practice. The SVG analogy doesn't hold (or I'm misunderstanding part of it). Let me explain and correct me if I got some of this wrong (apologies, I'm new to this spec). Let's say we're transitioning a 100x100 element that's 10px blurry from all sides. This would snapshot a 120x120 image, that according to this resolution would appear to the web developer as a 100x100 image. Let's say that the developer changes the `object-view-box` of the pseudo-element to be the top left quarter (0,0 50x50). What happens to the ink overflow/the blurry part? Given that * is the blurry part and 0 is the content, which one is it? ``` *** *00 ``` or ``` **** *00* **** ``` ? The former doesn't seem like what the developer intended, and the latter would require keeping the filter information as part of the transition so that we could re-apply the blur, which seems like a big change. In SVG this is not a problem since the ink-overflow bit can be derived from the SVG and CSS. But here all we have is a previously snapshotted image. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8597#issuecomment-1537440283 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 7 May 2023 13:16:39 UTC