- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Mar 2023 22:11:58 +0000
- To: public-css-archive@w3.org
As noted in #8581, we could also introduce a new future-proof syntax that avoids ambiguities (while keeping the existing one for legacy reasons, of course). The syntax suggested in the other issue uses slashes to distinguish the values: ```ebnf <spread-shadow> = <modern-spread-shadow-syntax> | <legacy-spread-shadow-syntax> <modern-spread-shadow-syntax> = <'box-shadow-color'>? && [ <'box-shadow-offset'> [ / <'box-shadow-blur'> [ / <'box-shadow-spread'> ]? ]? ] && <'box-shadow-position'>? <legacy-spread-shadow-syntax> = <'box-shadow-color'>? && [ <'box-shadow-offset'> [ <'box-shadow-blur'> <'box-shadow-spread'>? ]? ] && <'box-shadow-position'>? ``` Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8568#issuecomment-1468909579 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 March 2023 22:12:00 UTC