- From: shans via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 May 2016 21:42:45 +0000
- To: public-houdini-archive@w3.org
The CSSTokenStream object represents values which are literally not parsed yet. As in, no engine has parsed them. When they become parsed they stop being CSSTokenStream objects. While engines are free to tokenize up-front, it is not a goal of the typed OM to expose internal vendor-specific implementation details. Your example above doesn't demonstrate that the values are parsed. Instead it demonstrates that the value has been rejected because of a parentheses mismatch. Look at any implementation of custom properties (or the specification for that matter) and you'll see that there is a parse step *after* substitution of custom property values. Also, I take strong exception to your rhetoric: * "Uh. That's terrible design." * "My issue with this is that it makes the whole API rather useless." The first statement is an unwarranted and unhelpful statement of personal opinion. The second, at best, is immediately demonstrably untrue. Please, either participate in a civil manner or do not participate. -- GitHub Notification of comment by shans Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/193#issuecomment-221105170 using your GitHub account
Received on Monday, 23 May 2016 21:42:48 UTC