- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 May 2024 15:34:54 +0000
- To: public-css-archive@w3.org
> Only reason to do this, is to enable clipping. Feels like a technicality that puts extra load on the author and also increases the number of captured elements. So if the element is container only, it's painted content draws into its ancestor's snapshot (as usual) but there is a group pseudo-element generated to mirror its geometry and parent its descendant named elements. If the goal is just to optimize out redundant snapshots, then the browser can do this automatically. If the container has no painted content, we optimize out its snapshot. So I'm hesitant to add this paradigm unless needed for a use-case, for example, the element has painted content which *needs* to draw into its ancestor instead of underneath its own group pseudo. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10334#issuecomment-2137708735 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 May 2024 15:34:55 UTC