- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Nov 2020 21:54:43 +0000
- To: public-css-archive@w3.org
I second that some things should not be escapable, such as `contain` or things like clips/bounds on iframes. I'm worried that a feature that says "i escape all of my ancestors clips" can break some optimizations that we may have. For e.g. strict containment essentially says that the elements bounds contain all of the pixels of its contents, which means that if the element is off-screen then you don't need to paint any of its subtree. If something can escape it though, this is no longer true. Did you have a specific set of things in mind that you think this property should ignore / escape? -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5699#issuecomment-724301053 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 9 November 2020 21:54:44 UTC