Intent to Implement: supported-color-schemes meta tag

119 views
Skip to first unread message

Dominic Mazzoni

unread,
Jan 29, 2019, 11:54:54 AM1/29/19
to blink-dev, Emil A Eklund, fut...@chromium.org, tobi...@chromium.org, Aran Gilman

Contact emails

dmaz...@chromium.org, e...@chromium.org, fut...@chromium.org, tobi...@chromium.org, gilm...@google.com


Design doc/Spec

Apple proposed this here: https://github.com/w3c/csswg-drafts/issues/3299, and it's on the agenda to discuss at the upcoming CSSWG.


Summary

Many operating systems now have a "dark mode" preference. Some browsers already offer an option to transform webpages into a dark theme. The prefers-color-scheme media query is a way for an author to support their own dark theme, so they have full control over their own experience. The meta tag is needed so that a site can explicitly opt-in and say that they fully support a dark theme and that the browser should load a different UA sheet and not ever apply transformations.


Motivation

Without this, it's impossible for transformations applied by the browser (a "smart invert" feature, or other force-dark mode) and the prefers-color-scheme media query to coexist.


Risks

One open question is if we should put this in the manifest instead. We believe that the meta tag is still important because it gives us important rendering information early in parsing, but also supporting a similar property in the manifest would be reasonable.


Interoperability and Compatibility

Safari is the only one to ship prefers-color-scheme so far, and they're the ones who proposed this change too, so the risk seems low. We should strive to be compatible and take an opinionated stand on how web sites should support dark mode.


Conversations are ongoing with Microsoft.


Other public signals to be updated later.

Joe Medley

unread,
Jan 29, 2019, 12:16:28 PM1/29/19
to Dominic Mazzoni, blink-dev, Emil A Eklund, Rune Lillesveen, tobi...@chromium.org, Aran Gilman
Dominic,

Your summary and motivation are nicely written and from the web developer's perspective. Combined, they would make an excellent summary for a Chrome Status entry. Please make one. That's probably more text than will fit in the summary box, so continue it on the comments box.

Thanks,
Joe
Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com | 816-678-7195
If an API's not documented it doesn't exist.


--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFz-FYxfgKGXU38KLxJfrXG%3DuRf7FtFsoANJ%3DR6kVQ9wrTJOfQ%40mail.gmail.com.

Adam Argyle

unread,
Jan 29, 2019, 2:08:35 PM1/29/19
to Joe Medley, Dominic Mazzoni, blink-dev, Emil A Eklund, Rune Lillesveen, tobi...@chromium.org, Aran Gilman
Agreed, very nice summary!



--


Adam Argyle

UX Engineer

Seattle, WA

Dominic Mazzoni

unread,
Feb 4, 2019, 2:40:30 PM2/4/19
to Adam Argyle, Joe Medley, blink-dev, Emil A Eklund, Rune Lillesveen, tobi...@chromium.org, Aran Gilman

Joe Medley

unread,
Feb 4, 2019, 5:16:02 PM2/4/19
to Dominic Mazzoni, Adam Argyle, blink-dev, Emil A Eklund, Rune Lillesveen, tobi...@chromium.org, Aran Gilman
Thanks!

Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com | 816-678-7195
If an API's not documented it doesn't exist.

Rune Lillesveen

unread,
May 14, 2019, 7:39:38 AM5/14/19
to Dominic Mazzoni, Adam Argyle, Joe Medley, blink-dev, Emil A Eklund, tobi...@chromium.org, Aran Gilman
On Mon, Feb 4, 2019 at 8:40 PM Dominic Mazzoni <dmaz...@chromium.org> wrote:

I've updated the feature name to color-scheme and spec reference to reflect the current status.
Reply all
Reply to author
Forward
0 new messages