- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Sep 2024 15:31:40 +0000
- To: public-css-archive@w3.org
> So if a function accepts a single parameter, then f({a}) uses {a} as the argument, but then if we add a 2nd optional parameter, then the argument will suddenly change to a? Seems bad for forwards compatibility.
I'm not sure what you mean by this. What's the grammar for that first argument? If it's a comma-containing production, then `f({a})` would be taking `a` as the argument. If it's anything else, it's almost certain that `{a}` would just be invalid, but if we ever *do* define an actual grammar taking that on purpose, it woudl work as normal.
The presence or absence of a second argument, optional or not, has nothing to do with this, and I'm not sure how you're reading that into what I wrote.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9539#issuecomment-2374427551 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 September 2024 15:31:41 UTC