Skip to content
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

[css-contain] Move inline-size containment to the Level 2 spec #7631

Conversation

sideshowbarker
Copy link
Contributor

@sideshowbarker sideshowbarker commented Aug 20, 2022

https://wpt.fyi/results/css/css-contain mostly shows green for all engines for the variouscontain-inline-* tests (though Safari seems to be failing 100% of the https://wpt.fyi/results/css/css-contain/contain-inline-size-replaced.html tests…)

That’d seem to suggest the “inline-size containment” feature is sufficiently mature enough to move into the Level 2 spec.

@w3cbot
Copy link

w3cbot commented Aug 20, 2022

sideshowbarker marked as non substantive for IPR from ash-nazg.

@dbaron
Copy link
Member

dbaron commented Aug 22, 2022

This feature is closely tied to much of the other material in contain level 3 -- it's an important prerequisite for container queries. Given that container query implementation is happening (I think) in multiple engines, I think this may be a somewhat temporary situation, and I suspect that many other features in contain-3 are likely to show similar level of stability in the near future.

@sideshowbarker
Copy link
Contributor Author

Going ahead and closing this per #7631 (comment)

@sideshowbarker sideshowbarker deleted the sideshowbarker/inline-size-containment-move-to-level2 branch November 2, 2022 04:08
@syncbot syncbot restored the sideshowbarker/inline-size-containment-move-to-level2 branch January 12, 2023 06:16
@plinss plinss deleted the sideshowbarker/inline-size-containment-move-to-level2 branch January 12, 2023 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants