CSS WG Blog – Minutes Toronto F2F 2019-06-05 Part II: CSS Color 5; CSS Text 4; Backgrounds and Borders; Color Adjust; Media Queries

Minutes Toronto F2F 2019-06-05 Part II: CSS Color 5; CSS Text 4; Backgrounds and Borders; Color Adjust; Media Queries

By Dael Jackson July 6, 2019 (Permalink)
Categories: resolutions

Resolved: Put all the proposals into css-color-5, ChrisL and future Una as editors
Resolved: Rename to put ‘color’ first, adjust-color -> color-mod
Resolved: Add color-contrast without currentBackground option
- Question of “is computed value a color or a contrast-color”?
Resolved: Add color-mix, try to align syntax with cross-fade
Resolved: Put both color adjustment proposals into css-color-5, with keywords instead of underscores for Lea’s proposal
- Proposal A
- Proposal B
Resolved: Add Lea Verou as editor of css-color-5

Resolved: Drop the less useful values [notch & scoop], and rename [bevel -> angle] as proposed in the issue (Issue #3457: Borders with cut corners)

Resolved: Add a note to color-scheme to warn authors that dark and light modes are not necessarily black and white colors, and that if they are specifying any of their own colors they should specify enough colors to satisfy WCAG requirements (with a link) (Issue #3983: Clearly define what ‘light’ and ‘dark’ mean)
There was heavy disagreement as to if the spec should also include a note that both foreground and background should be specified in pairs. Due to the lack of consensus the pairs section of text was not added to the spec.

There was support for allowing prefers-color-scheme to expose subsets of color-scheme in the future. Without user agents expressing a desire to implement any additional color schemes it was decided that it was too early to add this to spec and instead it was important to avoid writing spec text that would prevent this in the future.
Resolved: No change (Issue #3853: Future custom-ident value sepia)

There was disagreement on the purpose of the no-preference value for prefers-color-scheme (Issue #3857: UA guidance on light vs no-preference).
Part of the group argued that the default state of the web is no-preference where designers create their own look, but the other side said that a majority of the web is already light so the reality is the default would equal light already.
Windows has three options for color schemes (light, dark, system default), but macOS only has two (light and dark)
There was concern that three values would lead to designers feeling the need to create color schemes instead of two (rather than letting no-preference share with either light or dark).

Last updated 2019-07-06 23:32:05