- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Mar 2023 12:57:52 +0000
- To: public-fxtf-archive@w3.org
cdoublev has just created a new issue for https://github.com/w3c/fxtf-drafts: == [motion-1] `offset-path` should accept `<url>` instead of `<url()>` == I suspect the intended production is `<url>`, which also accepts `<src()>`. https://drafts.fxtf.org/motion-1/#typedef-offset-path --- **Aside** `<url()>` and `<src()>` are never defined with their own production rules: > The `<url>` type, written with the `url()` and `src()` functions, represents a URL, which is a pointer to a resource. > > The syntax of `<url>` is: > > ``` > <url> = url( <string> <url-modifier>* ) | > src( <string> <url-modifier>* ) > ``` > > For legacy reasons, a `url()` can be written without quotation marks around the URL itself, in which case it is specially-parsed as a `<url-token>` https://drafts.csswg.org/css-values-4/#url-value Therefore I considered `<url-token>` as a replacement of `<url>`, instead of increasing maintenance cost with a "custom" production rule. Ideally: ``` <url> = <url()> | <src()> <url()> = url( <string> <url-modifier>* ) | <url-token> <src()> = src( <string> <url-modifier>* ) ``` Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/508 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 12:57:54 UTC