W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2009

[whatwg] Inconsistent behavior for empty-string URLs

From: Nicholas Zakas <nzakas@yahoo-inc.com>
Date: Tue, 15 Dec 2009 16:11:57 -0800
Message-ID: <4E45EC6AD219FD47AD1BC06E4EE3845D0420D446@SNV-EXVS09.ds.corp.yahoo.com>
Here's what I would propose:

1. Empty string attributes for HTML elements specifying resources to
automatically download are considered invalid and don't cause a request
to be sent. Examples: <img>, <link>, <script>, <iframe>, etc. This would
not apply to <a href=""> because it is a user-initiated request.

2. This also applies to manipulation of HTML elements through the DOM,
so (new Image()).src="" would not result in a request being sent.

3. This does not apply to JavaScript APIs that are unrelated to HTML
elements, such as Web Workers, XMLHttpRequest, etc.


-Nicholas
 
______________________________________________
Commander Lock: "Damnit Morpheus, not everyone believes what you
believe!"
Morpheus: "My beliefs do not require them to."

-----Original Message-----
From: Jonas Sicking [mailto:jonas@sicking.cc] 
Sent: Tuesday, December 15, 2009 11:47 AM
To: Nicholas Zakas
Cc: Maciej Stachowiak; whatwg at lists.whatwg.org; Aryeh Gregor; Simon
Pieters
Subject: Re: [whatwg] Inconsistent behavior for empty-string URLs

On Tue, Dec 15, 2009 at 11:14 AM, Nicholas Zakas <nzakas at yahoo-inc.com>
wrote:
> Is it necessary to apply this within XSLT and CSS as well? Or is it
> possible to have this be an HTML-only feature? I'd be happy with the
> latter.

Nothing is required. But we do need a concrete proposal that everyone
agrees on.

/ Jonas
Received on Tuesday, 15 December 2009 16:11:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:54 UTC