- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Jul 2023 15:52:00 +0000
- To: public-css-archive@w3.org
faceless2 has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-link-params] URL fragments should be consistent with existing SVG fragments == It's unclear how the format for parameters encoded in a URL are supposed to play with existing URL fragments in SVG. The current SVG spec lets you combine a _timesegment_ (eg `t=10`) with (for example) a _spacesegment_ (eg `xywh=10,10,20,20` by separating them with an ampersand: `test.svg#t=10&xywh=10,10,20,20`. The `css-linked-params` spec is silent on how to combine these existing segment parameters with `param()`, but presumably we'd use the same model `test.svg#t=10&xywh=10,10,20,20¶m(--foo%20blue)`? The spec could do with specifying this. Secondly, assuming we go this way it feels inconsistent that if we have multiple parameters, we _don't_ use an ampersand to separate them * `test.svg#t=10&xywh=10,10,20,20¶m(--foo%20blue)param(--bar%20red)` * `test.svg#t=10&xywh=10,10,20,20¶m(--foo%20blue)¶m(--bar%20red)` The second one feels more correct to me, but at the moment the spec says no ampersand is used. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9051 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 July 2023 15:52:02 UTC