Re: [css-houdini-drafts] [css-typed-om]: There's no nice way to represent CSSUnparsedValue as a "list-plus" style object.

So anyway, *regardless* of whether we decide to accept raw Arrays for things that are list-like (in addition to the bespoke objects), we still have the issue that, if the bespoke objects are Array-like but we can't intercept sets, we still need to verify the correctness of the data on *every single set*, whereas that's unnecessary for every single other object in the entire Typed OM.

(On that tangent - we *do* plan to accept doubles anytime we'd accept a CSS `<number>`, and DOMStrings anytime we'd accept a CSS keyword, so there's precedent for "accept an Array anytime we'd accept a list-valued property value".)

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

Received on Wednesday, 19 April 2017 06:33:06 UTC