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

I had to drop before the end of the discussion, but I don't think @flackr's use case is particularly concerning: if you rotate your device, and then this makes the element with `content-visibility: auto` become visible, then it will stop skipping its contents and it will remember the new size. If it stays off-screen then it will keep the old size, which may not be the right one in the current orientation, but the user doesn't see it and if it ever becomes visible again it will get the right size. The only problem could be that when 1px becomes visible, the new size can be bigger and then for the user it may be a sudden apparition of e.g. 100px. But this is mitigated when the implementation uses a margin: https://drafts.csswg.org/css-contain/#relevant-to-the-user

> The element is "on-screen": its [paint containment box](https://drafts.csswg.org/css-contain/#paint-containment-box)'s [overflow clip edge](https://drafts.csswg.org/css-overflow-4/#overflow-clip-edge) intersects with the viewport, or a user-agent defined margin around the viewport.
> Note: This margin is meant to allow the user agent to begin preparing for an element to be in the viewport soon. A margin of 50% is suggested as a reasonable default.

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


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

Received on Wednesday, 22 February 2023 19:21:57 UTC