W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] [CSS2] empty url() behaviour needs errata to match Level 3

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Mon, 02 Jul 2018 23:54:42 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-401971604-1530575681-sysbot+gh@w3.org>
The Working Group just discussed `empty url behavior`, and agreed to the following:

* `RESOLVED: Empty URLs are treated as "about:invalid"`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: empty url behavior<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/2211<br>
&lt;fantasai> ScribeNick: fantasai<br>
&lt;fantasai> TabAtkins: url() function with empty string as its argument...<br>
&lt;fantasai> TabAtkins: I changed spec ot match behavior of empty resource requests in HTML<br>
&lt;fantasai> TabAtkins: and y'all reverted the change because you didn't understand why I did it<br>
&lt;fantasai> TabAtkins: Answer is to be consistent with HTML!<br>
&lt;fantasai> TabAtkins: Empty URL is technically a relative URL to the resource itself<br>
&lt;fantasai> TabAtkins: But e.g. in HTML &lt;img src=""> doesn't load the resource<br>
&lt;fantasai> TabAtkins: Empty URLs will still resolve in some cases, like in links<br>
&lt;fantasai> TabAtkins: But not for resource loading like this. Makes no sense to load the CSS stylesheet as an image of itself.<br>
&lt;fantasai> ...<br>
&lt;fantasai> chris: Do we expose imports in the OM, and would ...??<br>
&lt;fantasai> TabAtkins: I don't know<br>
&lt;fantasai> TabAtkins: But recursively attaching the same URL again wouldn't be useful<br>
&lt;fantasai> TabAtkins: I would like it to automatically fail, invalid URL.<br>
&lt;fantasai> tantek: But not invalid syntax<br>
&lt;fantasai> TabAtkins: No, not invalid syntax<br>
&lt;fantasai> TabAtkins: There's no place in CSS where resolving the URL as the URL of the stylesheet would be useful<br>
&lt;fantasai> TabAtkins: Proposal is that the empty URL, rather than being treated as a relative URL, is treated as an invalid URL<br>
&lt;fantasai> TabAtkins: Computed value is still an empty string, just treated like 'about:invalid'<br>
&lt;fantasai> TabAtkins: There should be no noticeable behavior difference, since the stylesheet is not a valid image/etc.<br>
&lt;tantek> +1<br>
&lt;fantasai> Rossen: Other comments?<br>
&lt;fantasai> RESOLVED: Empty URLs are treated as "about:invalid"<br>
&lt;TabAtkins> ScribeNick: TabAtkins<br>
&lt;TabAtkins> Rossen: So this is the last Values 3 issue.<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2211#issuecomment-401971604 using your GitHub account
Received on Monday, 2 July 2018 23:54:52 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:51 UTC