@@ -80,7 +80,7 @@ Opting Into a Preferred Color Scheme: the 'color-scheme' property {#color-scheme
8080
8181 <pre class=propdef>
8282 Name : color-scheme
83- Value : auto | only? && [ light | dark | <<custom-ident>> ]+
83+ Value : auto | [ light | dark | <<custom-ident>> ]+ | only && light
8484 Initial : auto
8585 Applies to : all elements
8686 Inherited : yes
@@ -130,13 +130,20 @@ Opting Into a Preferred Color Scheme: the 'color-scheme' property {#color-scheme
130130 is valid but has no additional effect
131131 beyond what the first instance of the keyword provides.
132132
133- : <dfn lt=only>only? </dfn>
133+ : <dfn lt=only>only</dfn>
134134 :: If provided,
135135 ''only'' indicates that the element <em> must</em> be rendered with one of the specified color schemes,
136136 if possible,
137137 even if the user's preference is for a different color scheme.
138138
139- Authors <em> should not</em> use this value,
139+ Issue: Per spec, ''only'' can only be used with ''light'' .
140+ Apple's implementation allows it with ''dark'' as well.
141+ The concern with ''only dark'' is that pages won't consider UAs that can't support ''dark'' schemes,
142+ and will thus render brokenly.
143+ This value might be expanded to all schemes or removed entirely
144+ depending on further consideration.
145+
146+ Authors <strong> should not</strong> use this value,
140147 and should instead ensure that their page renders well with whatever color scheme the user prefers
141148 (using the '@media/prefers-color-scheme' media query to adjust styles accordingly).
142149 This keyword is provided only for the rare cases where that might not be reasonably possible,
0 commit comments