- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jul 2024 15:19:17 +0000
- To: public-css-archive@w3.org
Summary of internal discussion and #10587: WebKit has raised an implementation concern regarding displaying the live image twice. We see a few options on how to resolve this: 1. try to figure it out in implementations 2. make this implementation-defined (maybe less recommended, a new cross-browser difference) 3. not capture any pixels at all for off-screen elements, and find some way to reflect this to the developer (a pseudo-class?). This might break some use-cases such as morphing large out-of-viewport elements into small in-viewport elements. 4. Allow user-agents to capture a lower-resolution image for offscreen elements. This is already text to that effect [here](https://drafts.csswg.org/css-view-transitions-1/#capture-rendering-characteristics) with a different purpose, elements with a large ink overflow, we can tune it a bit to clarify that it also applies for out-of-viewport elements. I currently tend to like (4) as it allows optimizing the important things without totally breaking the user-experience or creating a new mental load on authors. It also allows different tiers of optimizations based on device/memory/whatever as the results are not web-observable and the tradeoff between performance and visual degradation can be played with. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8282#issuecomment-2245542731 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 July 2024 15:19:18 UTC