- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 May 2016 19:01:21 +0000
- To: public-houdini-archive@w3.org
It seems like this could be addressed just as well by us explicitly exposing the "parse as X property" function. Then you can just fill in the variables as you find them, concat everything to a single string, and pass to that function, getting back the result you want. Regarding your actual proposal, I'm not seeing how it helps much. It gives you the gross structure of the value, but nothing else. What are you planning to do with the value based on that? It also does precisely what I said I didn't want - exposes a *partial* parse, where *some* values are recognized and given real Typed OM values, while others are left as basically strings, based solely on whether CSS grammars generally consider them unambiguous or not. This sort of complexity isn't future-friendly, and I don't think is particularly author-friendly, either. (Your proposal is definitely *possible* - we *do* tokenize the value, and do a generic parse (per Syntax - assemble blocks/functions, but no grammar-checking), and *could* expose things like that. I just don't see what it really gets you. Beware attractive complexity without underlying use-cases!) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/208#issuecomment-221370374 using your GitHub account
Received on Tuesday, 24 May 2016 19:01:26 UTC