Skip to content

[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 #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
chromium-helper opened this issue Feb 22, 2023 · 2 comments
Labels
crbug:Blink>Layout File a crbug with Blink>Layout component css-contain-2 css-sizing-4

Comments

@chromium-helper
Copy link
Owner

CSSWG added the following resolution(s):

  • RESOLVED: content-visibility: auto forces contain-intrinsic-size to gain an auto value, and we'll define that auto value for contain-intrinsic-size so it works with all the current values, and then make sure that the last remembered size is forgotten when contain-intrinsic-size changes (specifying where in rendering step it happens) so we can deal with the cases that Rob brought up.

in w3c/csswg-drafts#8407 (comment)

@chrishtr chrishtr added the crbug:Blink>Layout File a crbug with Blink>Layout component label Feb 22, 2023
@chromium-helper
Copy link
Owner Author

I have filed crbug.com/1418453

That is all that can be done here, closing issue.

@chromium-helper
Copy link
Owner Author

CSSWG added the following resolution(s):

  • RESOLVED: The check mentioned by Vlad occurs at computed-value time

in w3c/csswg-drafts#8407 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crbug:Blink>Layout File a crbug with Blink>Layout component css-contain-2 css-sizing-4
Projects
None yet
Development

No branches or pull requests

2 participants