Hi guys, Sorry to pester, but I want to make sure this comes to resolution before it's forgotten. Any other feedback?
-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:[email protected]] Sent: Thursday, January 07, 2010 1:09 PM To: Nicholas Zakas Cc: Simon Pieters; Maciej Stachowiak; [email protected]; Aryeh Gregor Subject: Re: [whatwg] Inconsistent behavior for empty-string URLs On Thu, Jan 7, 2010 at 1:03 PM, Nicholas Zakas <[email protected]> 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
