Re: [css-houdini-drafts] TypedOM returning an array of strings isn't a helpful behavior

I don't like making an api less useful than it could just because 
someone hypothetically might get it wrong, but the "external variable"
 for value-customization points + "accept to parse values with 
variables references" counter-proposal you made would solve my main 
problem with the current situation so if you feel more willing to 
pursue this approach than mine, that is an acceptable resolution to 
this issue.

My general parsing problem could technically be solved by a 
general-purpose parsing api like ```css-parse```, but I am sad I won't
 be able to use the result of this parsing directly into the typed om 
and will need to convert those things back to strings to apply them on
 the dom; that means my polyfills will not be able to take advantage 
of the efficiency of TypedOM when I've to support shorthand 
properties, but okay, that's not the end of the world.

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

Received on Tuesday, 24 May 2016 23:51:10 UTC