- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Apr 2023 05:12:04 +0000
- To: public-css-archive@w3.org
> 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 If the contain-intrinsic size changed it is very likely that the layout has changed in a way that affects the size of the item. If we assume the remembered size is almost certainly wrong then it seems pointless to remember it over resetting everything to a uniform size - the newly specified contain intrinsic size - which is likely to be a better guess for the size. > 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. I disagree that this is the *only* problem. Having vastly different sizes leads to large adjustments in scroll size and position which makes things strange for users dragging scrollbars. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8407#issuecomment-1496927111 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 April 2023 05:12:06 UTC