- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Mar 2023 23:36:47 +0000
- To: public-css-archive@w3.org
emilio has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-contain] content-visibility: auto visibility check timing needs details == https://drafts.csswg.org/css-contain/#cv-notes has: > The initial determination of visibility for [content-visibility: auto](https://drafts.csswg.org/css-contain/#propdef-content-visibility) must happen in the same frame that determined an existence of a new content-visibility: auto element. When and how, exactly? This is not really implementable without more details. Since the visibility check is usually done with an intersection observer, but intersection observer callbacks happen async per spec (https://w3c.github.io/IntersectionObserver/#queue-intersection-observer-entry-algo), how is this supposed to happen in the same frame? Does that mean that computing the intersections of the frame can change layout, and thus can change whether other stuff intersects? I hope not... cc @chrishtr @asurkov @mrobinson @Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8542 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 March 2023 23:36:49 UTC