- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Nov 2021 17:34:06 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-values-4] Clarify that function component values need to be followed by parentheses`, and agreed to the following: * `RESOLVED: Add this to the Value Definition Grammar` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: [css-values-4] Clarify that function component values need to be followed by parentheses<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/5728<br> <emilio> fantasai: So tab added bikeshed functionality in which he can link to a function definition using `<ident()>`<br> <emilio> fantasai: but this is not actually valid according to our value definition grammar<br> <fantasai> <'property-name'><br> <fantasai> <keyword><br> <emilio> ... that has quoted property references and terminal kws (^)<br> <emilio> ... so should we add this to the value-definition grammar and update all specs to use this convention?<br> <emilio> ... a subtle thing is that only terminals that represent a function will use this<br> <emilio> ... historically we haven't done this, e.g., `<url>`<br> <emilio> ... so the question is do we want to extend our syntax in this way<br> <fantasai> chris_: I would find this useful, have needed <foo> vs <foo()><br> <fantasai> astearns: So proposal is to add <name()> to our grammar<br> <fantasai> s/grammar/grammar for specs/<br> <fantasai> astearns: Will that require going back and fixing everything?<br> <fantasai> fantasai: I think it would be useful to make things consistent<br> <fantasai> fantasai: but I wouldn't do it for <url><br> <fantasai> astearns: If not required, it's better; would prefer not to mess with old things<br> <fantasai> astearns: Any other opinions?<br> <fantasai> RESOLVED: Add this to the Value Definition Grammar<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5728#issuecomment-971802978 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 November 2021 17:34:07 UTC