Peningkatan gaya default mode gelap dengan properti CSS skema warna dan tag meta yang sesuai
NS color-scheme CSS property and the corresponding meta tag allow developers to opt their pages in to the theme-specific defaults of the user agent stylesheet.
Diperbarui
Isi
Background #
NS prefers-color-scheme user preference media feature #
NS prefers-color-scheme user preference media feature gives developers full control over their pages’ appearances. If you are unfamiliar with it, please read my article prefers-color-scheme: Hello darkness, my old friend, where I documented everything I know about creating amazing dark mode experiences.
One puzzle piece that was only mentioned briefly in the article is the color-scheme CSS property and the corresponding meta tag of the same name. They both make your life as a developer easier by allowing you to opt your page in to theme-specific defaults of the user agent stylesheet, such as, for example, form controls, scroll bars, as well as CSS system colors. At the same time, this feature prevents browsers from applying any transformations on their own.
The user agent stylesheet #
Before I continue, let me briefly describe what a user agent stylesheet is. Most of the time, you can think of the word user agent (UA) as a fancy way to say browser. The UA stylesheet determines the default look and feel of a page. As the name suggests, a UA stylesheet is something that depends on the UA in question. You can have a look at Chrome’s (and Chromium’s) UA stylesheet and compare it to Firefox’s atau Safari’s (and WebKit’s). Typically, UA stylesheets agree on the majority of things. For example, they all make links blue, general text black, and background color white, but there are also important (and sometimes annoying) differences, for instance, how they style form controls.
Have a closer look at WebKit’s UA stylesheet and what it does regarding dark mode. (Do a full text search for “dark” in the stylesheet.) The default provided by the stylesheet changes based on whether dark mode is on or off. To illustrate this, here is one such CSS rule using the :matches pseudo class and WebKit-internal variables like -apple-system-control-background, as well as the WebKit-internal preprocessor directive #if defined:
input,
input:matches([type="password"], [type="search"]) {
-webkit-appearance: textfield;
#if defined(HAVE_OS_DARK_MODE_SUPPORT) &&
HAVE_OS_DARK_MODE_SUPPORT
color: text;
background-color: -apple-system-control-background;
#else
background-color: white;
#endif
}You will notice some non-standard values for the color dan background-color properties above. Neither text nor -apple-system-control-background are valid CSS colors. They are WebKit-internal semantic colors.
Turns out, CSS has standardized semantic system colors. They are specified in CSS Color Module Level 4. For example, Canvas (not to be confused with the tag) is for the background of application content or documents, whereas CanvasText is for text in application content or documents. The two go together and should not be used in isolation.
UA stylesheets can use either their own proprietary or the standardized semantic system colors, to determine how HTML elements should be rendered by default. If the operating system is set to dark mode or uses a dark theme, CanvasText (or text) would be conditionally set to white, and Canvas (or -apple-system-control-background) would be set to black. The UA stylesheet then assigns the following CSS only once, and covers both light and dark mode.
body {
color: CanvasText;
background-color: Canvas
}NS color-scheme CSS property #
NS CSS Color Adjustment Module Level 1 specification introduces a model and controls over automatic color adjustment by the user agent with the objective of handling user preferences such as dark mode, contrast adjustment, or specific desired color schemes.
NS color-scheme property defined therein allows an element to indicate which color schemes it is comfortable being rendered with. These values are negotiated with the user’s preferences, resulting in a chosen color scheme that affects user interface (UI) things such as the default colors of form controls and scroll bars, as well as the used values of the CSS system colors. The following values are currently supported:
-
normalIndicates that the element is not aware of color schemes at all, and so the element should be rendered with the browser’s default color scheme. -
[ light | dark ]+Indicates that the element is aware of and can handle the listed color schemes, and expresses an ordered preference between them.
Providing both keywords indicates that the first scheme is preferred (by the author), but the second is also acceptable if the user prefers it instead.
In this list, light represents a light color scheme, with light background colors and dark foreground colors, whereas dark represents the opposite, with dark background colors and light foreground colors.
Peringatan: Previously, the specification allowed an additional value light only that indicated that the element had to be rendered with a light color scheme if possible, even if the user’s preference is for a different color scheme. Authors should not use this value, and should instead ensure their page renders well with whatever color scheme the user prefers.
For all elements, rendering with a color scheme should cause the colors used in all browser-provided UI for the element to match with the intent of the color scheme. Examples are scroll bars, spellcheck underlines, form controls, etc.
NS color-scheme CSS property can be used on both the :root level, as well as on an individual per-element level.
On the :root element, rendering with a color scheme additionally must affect the surface color of the canvas (that is, the global background color), the initial value of the color property, and the used values of the system colors, and should also affect the viewport’s scroll bars.
:root {
color-scheme: dark light;
}Honoring the color-scheme CSS property requires the CSS to be first downloaded (if it is referenced via ) and to be parsed. To aid user agents in rendering the page background with the desired color scheme immediately, a color-scheme value can also be provided in a elemen.
meta name="color-scheme" content="dark light">Combining color-scheme dan prefers-color-scheme #
Since both the meta tag and the CSS property (if applied to the :root element) eventually result in the same behavior, I always recommend specifying the color scheme via the meta tag, so the browser can adopt to the preferred scheme faster.
While for absolute baseline pages no additional CSS rules are necessary, in the general case you should always combine color-scheme dengan prefers-color-scheme. For example, the proprietary WebKit CSS color -webkit-link, used by WebKit and Chrome for the classic link blue rgb(0,0,238), has an insufficient contrast ratio of 2.23:1 on a black background and fails both the WCAG AA as well as the WCAG AAA requirements.
I have opened bugs for Chrome, WebKit, dan Firefox as well as a meta issue in the HTML Standard to get this fixed.
Interplay with prefers-color-scheme #
The interplay of the color-scheme CSS property and the corresponding meta tag with the prefers-color-scheme user preference media feature may seem confusing at first. In fact, they play together really well. The most important thing to understand is that color-scheme exclusively determines the default appearance, whereas prefers-color-scheme determines the stylable appearance. To make this clearer, assume the following page:
head>
meta name="color-scheme" content="dark light">
style>
fieldset {
background-color: gainsboro;
}
@media (prefers-color-scheme: dark) {
fieldset {
background-color: darkslategray;
}
}
style>
head>
body>
p>
Lorem ipsum dolor sit amet, legere ancillae ne vis.
p>
form>
fieldset>
legend>Lorem ipsumlegend>
button type="button">Lorem ipsumbutton>
fieldset>
form>
body>The inline CSS code on the page sets the
Indonesian 
English