- From: Tab Atkins Jr. <notifications@github.com>
- Date: Wed, 27 May 2020 16:46:54 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 27 May 2020 23:47:06 UTC
Rather than excluding particular syntaxes, I'd do something like > If |color| is an sRGB color, or can be converted to sRGB using solely information the user agent inherently knows (for example, `lab(...)` or `color(display-p3, ...)` can be converted to sRGB without outside knowledge, but `color(--custom-profile, ...)` would require finding a matching ''@color-profile'' rule), then convert it to sRGB and set |color| to the result. Otherwise, ERROR. ---- Also, note that in your spec, rather than having to write out the full `[=parse something according to a CSS grammar|parsing=]`, you can just write `[=CSS/parsing=]` and it'll link the same. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/760#issuecomment-635002728
Received on Wednesday, 27 May 2020 23:47:06 UTC