- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Aug 2016 16:39:41 +0000
- To: public-houdini-archive@w3.org
I would like to point out I (still) think using a property instead of making the instances be iterable is a good thing because whenever we are going to support new values that currenty are CSSTokenStreamValue/CSSUnparsedValue (for instance a CSS Shapes Typed OM), we would have to make CSSShapeValue itself be an iterable of String for that not to be a breaking change (and that wouldn't make sense to me). If we go the property route, we could move the property to CSSValue (and return a Frozen array containing one item, the cssText, for any value type except CSSUnparseValue which might return a bigger array since it could contain custom property references). In that case, CSSUnparsedValue would be an empty interface whose only purpose would be to clarify that the value has no other type. Maybe (just thinking out loud here) we can actually drop CSSUnparsedValue entirely, and decide to just leave unparsed things be a bare instance of CSSValue directly. I didn't think this through, though, but that looks reasonable at first glance. -- GitHub Notification of comment by FremyCompany Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/239#issuecomment-240471064 using your GitHub account
Received on Wednesday, 17 August 2016 16:39:47 UTC