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

Tweak <meta name=color-scheme> definition. #7226

Merged
merged 2 commits into from Oct 18, 2021
Merged

Conversation

emilio added a commit to emilio/web-platform-tests that referenced this pull request Oct 15, 2021
This makes the assumption that the initial browser's color-scheme is
light, which I think is a reasonable assumption to run these tests
under.

An alternative would have to allow both "light" and "dark" wherever we
check for "normal" now (which loses test coverage in practice), or I
could complicate the test to compute the initial color-scheme using an
iframe or what not (but that complicates everything more).
emilio added a commit to emilio/web-platform-tests that referenced this pull request Oct 15, 2021
…lor-scheme computed value (before whatwg/html#7226)

This makes the tests valid both with and without the spec change
proposed above. Will send a follow-up PR to test the spec change.

This makes the assumption that the initial browser's color-scheme is
light, which I think is a reasonable assumption to run these tests
under.

An alternative would have to allow both "light" and "dark" wherever we
check for "normal" now (which loses test coverage in practice), or I
could complicate the test to compute the initial color-scheme using an
iframe or what not (but that complicates everything more).
emilio added a commit to emilio/web-platform-tests that referenced this pull request Oct 15, 2021
emilio added a commit to web-platform-tests/wpt that referenced this pull request Oct 15, 2021
…lor-scheme computed value (before whatwg/html#7226)

This makes the tests valid both with and without the spec change
proposed above. Will send a follow-up PR to test the spec change.

This makes the assumption that the initial browser's color-scheme is
light, which I think is a reasonable assumption to run these tests
under.

An alternative would have to allow both "light" and "dark" wherever we
check for "normal" now (which loses test coverage in practice), or I
could complicate the test to compute the initial color-scheme using an
iframe or what not (but that complicates everything more).
emilio added a commit to emilio/web-platform-tests that referenced this pull request Oct 15, 2021
source Show resolved Hide resolved
source Show resolved Hide resolved
emilio added a commit to emilio/web-platform-tests that referenced this pull request Oct 15, 2021
Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

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

LGTM; I guess we should wait to merge until the CSS PR is merged?

source Show resolved Hide resolved
@emilio
Copy link
Contributor Author

emilio commented Oct 16, 2021

LGTM; I guess we should wait to merge until the CSS PR is merged?

Done then :)

@emilio
Copy link
Contributor Author

emilio commented Oct 16, 2021

Filed https://bugs.chromium.org/p/chromium/issues/detail?id=1260617 for Chrome (referenced in the PR description too)

@domenic domenic merged commit 8e301e8 into whatwg:main Oct 18, 2021
domenic pushed a commit to web-platform-tests/wpt that referenced this pull request Oct 25, 2021
@emilio emilio deleted the color-scheme branch October 27, 2021 14:09
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this pull request Oct 29, 2021
…heme> to not depend on the color-scheme computed value (before whatwg/html#7226), a=testonly

Automatic update from web-platform-tests
Change wpt tests for <meta name=color-scheme> to not depend on the color-scheme computed value (before whatwg/html#7226)

This makes the tests valid both with and without the spec change
proposed above. Will send a follow-up PR to test the spec change.

This makes the assumption that the initial browser's color-scheme is
light, which I think is a reasonable assumption to run these tests
under.

An alternative would have to allow both "light" and "dark" wherever we
check for "normal" now (which loses test coverage in practice), or I
could complicate the test to compute the initial color-scheme using an
iframe or what not (but that complicates everything more).

--

wpt-commits: 705c808e7a972bc3454f1842cd73f1e85ee31818
wpt-pr: 31268
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this pull request Oct 29, 2021
…t create a pres hint., a=testonly

Automatic update from web-platform-tests
Assert that color-scheme meta tag doesn't create a pres hint

This tests the spec change in whatwg/html#7226.
--

wpt-commits: 13a5f1e14ff1ad575a46d03ea73c4f019f6e6036
wpt-pr: 31271
jamienicol pushed a commit to jamienicol/gecko that referenced this pull request Nov 1, 2021
…heme> to not depend on the color-scheme computed value (before whatwg/html#7226), a=testonly

Automatic update from web-platform-tests
Change wpt tests for <meta name=color-scheme> to not depend on the color-scheme computed value (before whatwg/html#7226)

This makes the tests valid both with and without the spec change
proposed above. Will send a follow-up PR to test the spec change.

This makes the assumption that the initial browser's color-scheme is
light, which I think is a reasonable assumption to run these tests
under.

An alternative would have to allow both "light" and "dark" wherever we
check for "normal" now (which loses test coverage in practice), or I
could complicate the test to compute the initial color-scheme using an
iframe or what not (but that complicates everything more).

--

wpt-commits: 705c808e7a972bc3454f1842cd73f1e85ee31818
wpt-pr: 31268
jamienicol pushed a commit to jamienicol/gecko that referenced this pull request Nov 1, 2021
…t create a pres hint., a=testonly

Automatic update from web-platform-tests
Assert that color-scheme meta tag doesn't create a pres hint

This tests the spec change in whatwg/html#7226.
--

wpt-commits: 13a5f1e14ff1ad575a46d03ea73c4f019f6e6036
wpt-pr: 31271
Gabisampaio pushed a commit to Gabisampaio/wpt that referenced this pull request Nov 18, 2021
…lor-scheme computed value (before whatwg/html#7226)

This makes the tests valid both with and without the spec change
proposed above. Will send a follow-up PR to test the spec change.

This makes the assumption that the initial browser's color-scheme is
light, which I think is a reasonable assumption to run these tests
under.

An alternative would have to allow both "light" and "dark" wherever we
check for "normal" now (which loses test coverage in practice), or I
could complicate the test to compute the initial color-scheme using an
iframe or what not (but that complicates everything more).
Gabisampaio pushed a commit to Gabisampaio/wpt that referenced this pull request Nov 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Consider changing specified behavior of <meta name=color-scheme> to match WebKit
3 participants