- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Nov 2021 22:55:45 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-contain] Consider top layer elements 'relevant to the user' for content-visibility: auto`, and agreed to the following: * `RESOLVED: If the subtree of an element contains a top-layer element it is relevent to the user` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-contain] Consider top layer elements 'relevant to the user' for content-visibility: auto<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/6727<br> <dael> vlad: Text says we skip the contents if the element is not relevnt to user. Defines relevent as things that have fosuc or selection<br> <Rossen_> q?<br> <dael> vlad: prop is add if content-visibility:auto descendant is in top level it is relevent and not skipped<br> <dael> chrishtr: Unskips content?<br> <dael> vlad: Yeah, if you have offscreen content-visbility:auto it would appear in the top layer and the subtree would be rendered<br> <dael> chrishtr: Entire tree including offscreen is relevent and not skipped<br> <dael> vlad: can't optimize out because have to display in top layer. Can't use same detection for visbility b/c escapes paint containment<br> <dael> vlad: If it escapse top layer assume it will be visible<br> <dael> chrishtr: If you have desc. of content-visbility:auto and you full screen the entire subtree will be made visbile<br> <dael> vlad: correct<br> <dael> chrishtr: including recursive ancestors. Okay. I think it's fine<br> <dael> Rossen_: Any other comments?<br> <dael> Rossen_: What's the prop text?<br> <dael> vlad: If the subtree of an element contains a top-layer element it is relevent to the user<br> <dael> Rossen_: Obj?<br> <dael> RESOLVED: If the subtree of an element contains a top-layer element it is relevent to the user<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6727#issuecomment-960260532 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 November 2021 22:55:47 UTC