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-conditional-5] Add 'none'-keywords to scroll-state() features #10874

Merged
merged 2 commits into from
Sep 18, 2024

Conversation

lilles
Copy link
Member

@lilles lilles commented Sep 12, 2024

Unintentionally left out in the original scroll-state() PR.

Unintentionally left out in the original scroll-state() PR.
@lilles lilles requested a review from dbaron September 12, 2024 07:41
aarongable pushed a commit to chromium/chromium that referenced this pull request Sep 12, 2024
The spec PR landed, so tests should now be supported by the spec.

The 'inset-' prefix for the stuck keywords per were not per spec and
remove both from tests and implementation.

The tests for the 'none'-keyword for snapped and stuck does not match
the current spec draft, but will be fixed by [1]

[1] w3c/csswg-drafts#10874

Bug: 40279568, 40268059
Change-Id: I7cf8d3a2f251eaea0c3a78329c46a7bfddd85dda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5850484
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1354415}
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request Sep 12, 2024
The spec PR landed, so tests should now be supported by the spec.

The 'inset-' prefix for the stuck keywords per were not per spec and
remove both from tests and implementation.

The tests for the 'none'-keyword for snapped and stuck does not match
the current spec draft, but will be fixed by [1]

[1] w3c/csswg-drafts#10874

Bug: 40279568, 40268059
Change-Id: I7cf8d3a2f251eaea0c3a78329c46a7bfddd85dda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5850484
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1354415}
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request Sep 12, 2024
The spec PR landed, so tests should now be supported by the spec.

The 'inset-' prefix for the stuck keywords per were not per spec and
remove both from tests and implementation.

The tests for the 'none'-keyword for snapped and stuck does not match
the current spec draft, but will be fixed by [1]

[1] w3c/csswg-drafts#10874

Bug: 40279568, 40268059
Change-Id: I7cf8d3a2f251eaea0c3a78329c46a7bfddd85dda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5850484
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1354415}
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this pull request Sep 16, 2024
…ests to wpt, a=testonly

Automatic update from web-platform-tests
[@container] Move scroll-state() query tests to wpt

The spec PR landed, so tests should now be supported by the spec.

The 'inset-' prefix for the stuck keywords per were not per spec and
remove both from tests and implementation.

The tests for the 'none'-keyword for snapped and stuck does not match
the current spec draft, but will be fixed by [1]

[1] w3c/csswg-drafts#10874

Bug: 40279568, 40268059
Change-Id: I7cf8d3a2f251eaea0c3a78329c46a7bfddd85dda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5850484
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1354415}

--

wpt-commits: d2c522e29aa466bbfcc863b51aa3556aff5a248c
wpt-pr: 48116
i3roly pushed a commit to i3roly/firefox-dynasty that referenced this pull request Sep 17, 2024
…ests to wpt, a=testonly

Automatic update from web-platform-tests
[@container] Move scroll-state() query tests to wpt

The spec PR landed, so tests should now be supported by the spec.

The 'inset-' prefix for the stuck keywords per were not per spec and
remove both from tests and implementation.

The tests for the 'none'-keyword for snapped and stuck does not match
the current spec draft, but will be fixed by [1]

[1] w3c/csswg-drafts#10874

Bug: 40279568, 40268059
Change-Id: I7cf8d3a2f251eaea0c3a78329c46a7bfddd85dda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5850484
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1354415}

--

wpt-commits: d2c522e29aa466bbfcc863b51aa3556aff5a248c
wpt-pr: 48116
jamienicol pushed a commit to jamienicol/gecko that referenced this pull request Sep 17, 2024
…ests to wpt, a=testonly

Automatic update from web-platform-tests
[@container] Move scroll-state() query tests to wpt

The spec PR landed, so tests should now be supported by the spec.

The 'inset-' prefix for the stuck keywords per were not per spec and
remove both from tests and implementation.

The tests for the 'none'-keyword for snapped and stuck does not match
the current spec draft, but will be fixed by [1]

[1] w3c/csswg-drafts#10874

Bug: 40279568, 40268059
Change-Id: I7cf8d3a2f251eaea0c3a78329c46a7bfddd85dda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5850484
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1354415}

--

wpt-commits: d2c522e29aa466bbfcc863b51aa3556aff5a248c
wpt-pr: 48116
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.

This is largely reasonable. However, I took a slightly deeper look at the issues related to evaluating in a boolean context, and I realize that there's no general statement about features being usable in a boolean context for container features, like there is for media features.

It might be better to add a paragraph in the introduction to container features that repeats the first two paragraphs of https://drafts.csswg.org/mediaqueries-4/#mq-boolean-context (or refers to them). If you have that, then you don't need any mention of evaluation in a boolean context in the feature definitions at all.

And I think it's probably correct -- I'm guessing container features all evaluate in a boolean context just like media features do.

(On the other hand, I think it's ok to land this if you don't want to do that right now, but I think doing that should also be pretty straightforward.)

css-conditional-5/Overview.bs Outdated Show resolved Hide resolved
@lilles lilles merged commit 420269e into w3c:main Sep 18, 2024
1 check passed
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified-and-comments-removed that referenced this pull request Sep 20, 2024
…sts to wpt, a=testonly

Automatic update from web-platform-tests
[container] Move scroll-state() query tests to wpt

The spec PR landed, so tests should now be supported by the spec.

The 'inset-' prefix for the stuck keywords per were not per spec and
remove both from tests and implementation.

The tests for the 'none'-keyword for snapped and stuck does not match
the current spec draft, but will be fixed by [1]

[1] w3c/csswg-drafts#10874

Bug: 40279568, 40268059
Change-Id: I7cf8d3a2f251eaea0c3a78329c46a7bfddd85dda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5850484
Reviewed-by: Anders Hartvoll Ruud <andruudchromium.org>
Commit-Queue: Rune Lillesveen <futharkchromium.org>
Cr-Commit-Position: refs/heads/main{#1354415}

--

wpt-commits: d2c522e29aa466bbfcc863b51aa3556aff5a248c
wpt-pr: 48116

UltraBlame original commit: e2408da6c7247006aedbc2849c092ab49d07d898
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified that referenced this pull request Sep 20, 2024
…sts to wpt, a=testonly

Automatic update from web-platform-tests
[container] Move scroll-state() query tests to wpt

The spec PR landed, so tests should now be supported by the spec.

The 'inset-' prefix for the stuck keywords per were not per spec and
remove both from tests and implementation.

The tests for the 'none'-keyword for snapped and stuck does not match
the current spec draft, but will be fixed by [1]

[1] w3c/csswg-drafts#10874

Bug: 40279568, 40268059
Change-Id: I7cf8d3a2f251eaea0c3a78329c46a7bfddd85dda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5850484
Reviewed-by: Anders Hartvoll Ruud <andruudchromium.org>
Commit-Queue: Rune Lillesveen <futharkchromium.org>
Cr-Commit-Position: refs/heads/main{#1354415}

--

wpt-commits: d2c522e29aa466bbfcc863b51aa3556aff5a248c
wpt-pr: 48116

UltraBlame original commit: e2408da6c7247006aedbc2849c092ab49d07d898
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.

2 participants