- From: shans via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Oct 2017 00:25:26 +0000
- To: public-houdini-archive@w3.org
My first instinct is that parseAll should always return a sequence for the purposes of future-proofing (otherwise the return value might change if a property were promoted to list-valued in the future). However, something else I noticed - append() and set() can't take sequences, they need to take individual values. That makes parseAll more painful to use in some cases, as you need to prepend the property value then .apply the result to append/set. Maybe we should also modify these methods to take a list of both primitives and sequence args? -- GitHub Notification of comment by shans Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/502#issuecomment-340315671 using your GitHub account
Received on Monday, 30 October 2017 00:25:29 UTC