- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Oct 2018 22:30:19 +0000
- To: public-houdini-archive@w3.org
We haven't figured out the answer to this. :( I suspect this needs to be resolved by separating out the top-level *productions* of a property grammar into "list-valued" and "single-valued" categories, and throwing an error if you ever try to put a single-valued production into a list-valued mode. (Such as starting with "transform:none" and then appending a value, or vice versa.) Maybe we special-case list-based interaction with the "empty" values that some properties, like `transform`, have, so you can *start* from that value and append list-valued values and have it work "as expected"? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/823#issuecomment-427999687 using your GitHub account
Received on Monday, 8 October 2018 22:30:20 UTC