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

I would be ok with that. It would remain that the L1 spec would not 
cover a large class of my use cases for the spec but I never intended 
nor hinted I wished stopping the entire spec on this one class of use 
cases if you believe this issue isn't fixable in L1. 

The only thing I want to make sure of is that we have a path forward 
(so that we can possibly move from one solution to the other without 
breaking the web). I'll have a closer look later today, but I think it
 would be possible to move forward by adding a "content" property with
 more details in Level 2 (but only work as a string list now). 

I wonder if we could still make the 'CSSTokenStreamValue' not iterable
 and instead make it return a iterable with a ```cssTextGroups``` or 
```cssTextSlices``` property, that looks a small enough change what do
 you think?

As regard to the name, now that I understand the matter more clearly, 
what do you think of "CSSUnparsedValue"?

I'll open another issue later today for the broader parser-bail-out 
discussion once I investigated this more, I agree this thread moved 
beyond the initial topic (but I'll have you note it wasn't 
intentional, it started with a genuine question as to better 
understand why we needed another name).

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

Received on Monday, 23 May 2016 22:22:01 UTC