[csswg-drafts] [css-sizing] Should `contain-intrinsic-size: auto` really care about being relevant to the user for `content-visibility: hidden`? (#7521)

Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-sizing] Should `contain-intrinsic-size: auto` really care about being relevant to the user for `content-visibility: hidden`? ==
From https://drafts.csswg.org/css-sizing-4/#valdef-contain-intrinsic-width-auto-length

> If the element has a [last remembered size](https://drafts.csswg.org/css-sizing-4/#last-remembered), is currently [skipping its contents](https://drafts.csswg.org/css-contain-2/#skips-its-contents), and is not [relevant to the user](https://drafts.csswg.org/css-contain-2/#relevant-to-the-user), its [explicit intrinsic inner size](https://drafts.csswg.org/css-sizing-4/#explicit-intrinsic-inner-size) is the last remembered size.

Why check "not relevant to the user"? For `content-visibility: auto` it's fine, since it only skips its contents if not relevant to the user, so the conditions are equivalent.

But `content-visibility: hidden` always skips its contents. So having to check if it's relevant to the user means that the position of such elements will need to be tracked with `contain-intrinsic-size: auto`, even if `content-visibility: hidden` doesn't normally require so.

This was added in https://github.com/w3c/csswg-drafts/commit/839ae05a17e6fbda8b9643997f53eaa68548a0a9. Was it really needed?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7521 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 20 July 2022 20:52:43 UTC