- From: shans via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Aug 2016 01:19:08 +0000
- To: public-houdini-archive@w3.org
So I'm leaning towards something that looks like
```
[constructor(sequence<DOMString or CSSVariableReferenceValue>]
interface CSSTokenStreamValue : CSSStyleValue {
FrozenArray<(DOMString or CSSVariableReferenceValue)> components;
};
```
Purely because it seems to thread all the Opinions on display here.
If I could have magical ponies then I think CSSTokenStreamValue would
just be an array that subclasses CSSStyleValue, but it seems those are
somewhat in demand at the moment.
As a side note, y'all need some explainers about what current 'best
practise' is, preferably one that has been reviewed by the TAG as well
as all relevant JS vendor teams... I don't think the current drive-by
conflicting assertions approach is working.
--
GitHub Notification of comment by shans
Please view or discuss this issue at
https://github.com/w3c/css-houdini-drafts/issues/239#issuecomment-240287503
using your GitHub account
Received on Wednesday, 17 August 2016 01:19:15 UTC