Re: [css-houdini-drafts] [css-typed-om] Rename CSSTokenStream to something that doesn't talk about tokens

The canonically ambiguous example is colors.  `red` could a color (and
 thus returned as a CSSColor or whatever), or any other keyword in any
 context.  `#f00` could be a color (ditto), or be a hash.

I'm not super interested in trying to specify a best-effort "parse 
some of the values if you can" thing; it'll be (a) confusing for 
authors as some things get parsed and others don't, often for obscure 
grammar reasons (how many authors know about `nav-up`/etc?), and (b) 
future-hostile, as things become ambiguous or unambiguous as we change
 the language.

(I thought 2px was ambiguous, but it's probably not; I'm continually 
forgetting exactly what the value space of `font-family` is. (It's 
just `<string> | <custom-ident>+`.))

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at 
https://github.com/w3c/css-houdini-drafts/issues/193#issuecomment-221029576
 using your GitHub account

Received on Monday, 23 May 2016 16:52:17 UTC