- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Oct 2018 09:31:25 +0000
- To: public-houdini-archive@w3.org
Describing list-valuedness of productions rather than properties makes much more sense! Re. special-casery of "empty" values, something more general might be needed. Custom properties may have custom "empty" values, e.g. `omitted | <number>+`, and it's possible to register a property with several different incompatible lists: `<length>+ | <url>+`. Perhaps `append` should behave as `set` whenever you are trying to append something that's incompatible with the current value. Sidenote: the `<length>+ | <url>+`-case means that we have to reify the current value to check whether the `append` is allowed. (We may be attempting to append a list of urls to an existing list of lengths, or vice-versa). -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/823#issuecomment-428125370 using your GitHub account
Received on Tuesday, 9 October 2018 09:31:31 UTC