| 03:23 | <TabAtkins> | Domenic, annevk: Is https://drafts.csswg.org/css-color-adjust-1/#color-scheme-meta a sufficient definition for a new <meta name> value? |
| 03:24 | <Domenic> | TabAtkins: nah, needs to state things about inserting/removing/etc. E.g. https://html.spec.whatwg.org/multipage/semantics.html#meta-referrer . (There is some duplicate text between a few meta values we should eventually extract out.) |
| 03:24 | <Domenic> | Similarly needs to pick one winner if multiple exist |
| 03:25 | <TabAtkins> | It already picks a winner (first wins, per spec), but I can put in something that explicitly re-runs on mutation tomorrow. |
| 03:26 | <Domenic> | "first" in what ordering... |
| 03:27 | <TabAtkins> | ...document ordering? What other order could there be? |
| 03:27 | <Domenic> | shadow or not |
| 03:27 | <Domenic> | Do you want the first which parses correctly, or the the first that exists, or...? |
| 03:27 | <TabAtkins> | Ooofa, we out here respecting shadow dom in *<head>*? |
| 03:27 | <TabAtkins> | Yeah, I realized the "parses correctly" condition is important as I was thinking about mutation just now. ^_^ |
| 03:28 | <Domenic> | Well, you didn't restrict to head. |
| 03:28 | <Domenic> | I think the referrer algorithm is a pretty good model of precision and do suggest following it closely until such time as we factor it out :) |
| 03:29 | <TabAtkins> | Yeah, sounds good. Thanks! |
| 03:29 | <Domenic> | Also I guess for referrer we went with last-valid-one wins so that fallbacks would work as the value space evolved, interesting |
| 03:30 | <TabAtkins> | I'm going for first-wins because the whole point of this particular meta value is to let us correctly paint the screen asap; it's definitely not consistent with most other things, especially in CSS. |
| 03:31 | <Domenic> | Fair, I guess fallbacks probably still work |
| 03:31 | <TabAtkins> | Yeah, just have to order them differently than CSS does normally; newer syntax first. |
| 03:32 | <Domenic> | I guess theme-color also does first-wins, so that's at least comforting. |
| 03:37 | <TabAtkins> | Ah, nice. |
| 12:50 | <devsnek> | wasn't there supposed to be some standardized location for layered api polyfills |
| 15:46 | <Domenic> | TabAtkins or anyone: ELI5, is forced-colors ("high contrast") orthogonal to dark mode/light mode, or are they separate? E.g. if I am designing a control do I need 3 states (light, dark, forced colors) or some matrix (light, dark) x (unforced, forced) |
| 15:47 | <TabAtkins> | Separate, you need 3 states only. |
| 15:48 | <TabAtkins> | We'll get the forced-colors details in soon |
| 15:48 | <TabAtkins> | But yeah, forced overrides any other concerns |
| 21:06 | <TabAtkins> | Domenic, annevk: Can y'all put appropriate dfn attributes on the meta/name attribute definition? |
| 21:06 | <Domenic> | Sure, file an issue describing the problem. I guess the heuristics didn't work there for some reason. |