Skip to content

[css-contain][css-conditional] Move container queries from contain-3 to conditional-5 #10447

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

Merged
merged 4 commits into from
Jun 18, 2024

Conversation

frivoal
Copy link
Collaborator

@frivoal frivoal commented Jun 14, 2024

See #10433

This PR makes no change to the normative text, just moves it, and adjusts the relevant abstracts/introductions/changelogs/…

Copy link
Member

@dbaron dbaron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. A few comments below (which others may have thoughts on as well).

@@ -64,6 +94,11 @@ Introduction</h2>
such that only the first matching rule in a [=conditional rule chain=]
is applied.

It also adds Container Queries.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest changing the order of the description of the three new pieces (font technology queries, @when/@else, and Container Queries) of the introduction. Specifically:

  • I think the bit about querying for supported font technologies should be last, since it's probably the smallest both in scope and size.

  • I think the addition of container queries could optionally be before the introduction of @when and @else since I think CQ is a more significant feature but @when/@else could perhaps be described as having broader scope over the features of the module, so I could see describing these in either order.

@frivoal frivoal requested a review from dbaron June 17, 2024 07:36
Copy link
Contributor

@svgeesus svgeesus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with the comment from @dbaron about ordering. That aside, this all looks good.

@svgeesus svgeesus merged commit 02ecea2 into w3c:main Jun 18, 2024
1 check passed
frivoal added a commit to frivoal/wpt that referenced this pull request Jun 28, 2024
@frivoal frivoal added Closed Accepted by CSSWG Resolution Tested Memory aid - issue has WPT tests and removed Needs Feedback/Review labels Jun 28, 2024
frivoal added a commit to web-platform-tests/wpt that referenced this pull request Jun 28, 2024
i3roly pushed a commit to i3roly/firefox-dynasty that referenced this pull request Jul 9, 2024
…estonly

Automatic update from web-platform-tests
Move tests to match the spec's move

See w3c/csswg-drafts#10447

--

wpt-commits: c6273f7c688e8e62356f2a0a6e388108d58042ef
wpt-pr: 46928
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this pull request Jul 9, 2024
…estonly

Automatic update from web-platform-tests
Move tests to match the spec's move

See w3c/csswg-drafts#10447

--

wpt-commits: c6273f7c688e8e62356f2a0a6e388108d58042ef
wpt-pr: 46928
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants