Re: [w3c/manifest] Color processing steps are incorrect (#760)

The first three steps are all covered by just calling CSS/parse with a string. The end result is a `<color>` value, which you can then manipulate in prose, excluding things aren't convertible to RGBA (like `currentcolor` or `device-cmyk()`) and possibly excluding more difficult things (like `color()` with a non-builtin profile).  Step 4 is all past CSS Syntax tho, and into CSS Color.

(Like, if this kind of thing might be done elsewhere, it might be useful for CSS Color to go ahead and define a grammar nonterminal just for "canonicalizable to RGBA without outside information" colors, so you can just parse to that.)

---------

> but when following steps we then get to “from the list of tokens produced by the tokenizer” without further links or info about how to make a tokenizer.

You might be missing this introductory text from 5.3, which applies to all of the algorithms:

> They assume that they are invoked on a token stream, but they may also be invoked on a string; if so, first perform input preprocessing to produce a code point stream, then perform tokenization to produce a token stream.

Does that answer your question? If not, what exactly do you think is missing?

-- 
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-485561596