Re: [csswg-drafts] [css-contain] Behavior of slightly offscreen content having`content-visibility:auto` when UA margin around the viewport is 0 (#8407)

> I'm not sure what you mean with "not-relevant", I think it would make more sense to not skip its contents (as if relevant) so that it stays off-screen (as if not relevant)

I meant "not-relevant" as the opposite of ["relevant"](https://www.w3.org/TR/css-contain-2/#relevant-to-the-user), which means [skipping its contents](https://www.w3.org/TR/css-contain-2/#skips-its-contents)

> [Testcase](https://software.hixie.ch/utilities/js/live-dom-viewer/saved/11271)
This is a nice example to think about 👍 
Yes, in this case, not skipping the element having `content-visibility: auto` and `contain-intrinsic-height` (considering it as relevant) is clearly proper.

I want to pursue a way that improves rendering performance.
So I agree with keeping the offscreen elements as offscreen (skipped content).

But I'm not sure about classifying this circularity element as "maybe relevant", because the element will stay as offscreen always.
The user cannot see it, so it always won't be relevant to the user. (If we interpret "relevant to user" as "user can interact with this element")

Therefore, I'm curious about what will be the appropriate description to process the circularity element in terms of the spec:
- maybe relevant (maybe not skipped element), so `contain-intrinsic-size` won't be applied
- not relevant (skipped element), but `contain-intrinsic-size` won't be applied

-- 
GitHub Notification of comment by jihyerish
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8407#issuecomment-1427226651 using your GitHub account


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

Received on Monday, 13 February 2023 02:11:10 UTC