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

I hear you. I do have use cases, though. My two use cases are:

- **Use case 1**: When there is a calc expression involving a 
variable, I might want to animate some part of it and right now I 
can't -- I'm forced to parse the calc(...) string and reconcat 
everything to be set as a string (because there is no structure that 
exists which would help me set this as a typed value). 

  The intermediate structure I propose -- while not perfect -- would 
allow me to manipulate the structure to change just the part I need 
and set the property to this modified value, avoiding the use of 
strings altogether. Most of the times, what you need to change in a 
loop is a numeric expression.

- **Use case 2**: When I polyfill things like css-grid, there is no 
native property with a syntax close enough to help me in this case. 

 This basic syntax parsing would give me everything I need to build a 
light-weight transpiler to data structures that are useful to me, 
instead of forcing me to roll an entire css parser just for the 
purpose of understanding the basics which the browser already 
understands.

I believe the first use case is definitely a primary target for the 
spec. The second one is a requirement for me personally to use the API
 in most of my projects, but I can understand it might look like a 
secondary target only for the spec.

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

Received on Tuesday, 24 May 2016 19:40:19 UTC