- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Mar 2023 17:16:26 +0000
- To: public-fxtf-archive@w3.org
> I suspect the intended production is <url>, which also accepts <src()>.
Yup.
> <url()> and <src()> are never defined with their own production rules:
Because it isn't necessary for our purposes. ^_^ But I can do that, I suppose.
> Therefore I considered <url-token> as a replacement of <url>, instead of increasing maintenance cost with a "custom" production rule.
This is very much incorrect. *All* token productions are usually wrong for use as values directly, as they only correspond to particular literal syntaxes and don't allow for other ways of producing the same value.
But it's especially wrong for `<url>`, since `url(foo)` is a `<url-token>` but `url("foo")` is a `<function-token>` (followed by a string and a close-paren).
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/508#issuecomment-1468509788 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 17:16:27 UTC