[whatwg] Inconsistent behavior for empty-string URLs

Jonas Sicking jonas at sicking.cc
Thu Jan 7 13:09:07 PST 2010

On Thu, Jan 7, 2010 at 1:03 PM, Nicholas Zakas <nzakas at yahoo-inc.com> wrote:
> I'm going to take a lack of response to this question as a "no". :)
> Given the disparate browser implementations for dealing with empty
> string URLs, it seems unlikely that anyone is relying upon the current
> behaviors, so I'd like to suggest this change be added to HTML5:
> For any <img>, <link>, <script>, <iframe>, <audio>, <video>, <audio>,
> <object>, <embed>, <input>, <html manifest>, or <frame> tag that will
> result in an automatic download of an external resource must ignore any
> empty string URL and not download the external resource. This is true
> even when a <base href> is applied to the page.
> Does that sound right?

Sounds good to me.

/ Jonas

More information about the whatwg mailing list