- From: Sam Atkins via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Apr 2025 09:59:04 +0000
- To: public-css-archive@w3.org
AtkinsSJ has just created a new issue for https://github.com/w3c/csswg-drafts:
== [cssom] "Serialize a URL" lacks support for url-modifiers and src() ==
The [current spec](https://drafts.csswg.org/cssom-1/#serialize-a-url) says:
> To serialize a URL means to create a string represented by "url(", followed by the [serialization](https://drafts.csswg.org/cssom-1/#serialize-a-string) of the URL as a string, followed by ")".
As mentioned in the title, there are a couple of gaps here:
1. ["Serialize a CSS value"](https://drafts.csswg.org/cssom-1/#serialize-a-css-value) serializes all `<url>` values as above, which would mean `src(...)` is serialized as `url(...)`. Is this intentional?
2. `url()` and `src()` can both take a list of `<url-modifier>`s, which are missed out here. This means for example that `url("https://example.com" crossorigin(anonymous))` would serialize as `url("https://example.com")`.
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12057 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 April 2025 09:59:05 UTC