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: Thu, 10 Dec 2009 10:22:59 -0800
Message-ID: <4E45EC6AD219FD47AD1BC06E4EE3845D0420D0B5@SNV-EXVS09.ds.corp.yahoo.com>
Sweet, so how can we get this done? :)

-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: Wednesday, December 09, 2009 2:56 PM
To: Nicholas Zakas
Cc: Simon Pieters; Aryeh Gregor; whatwg at lists.whatwg.org
Subject: Re: [whatwg] Inconsistent behavior for empty-string URLs

On Wed, Dec 9, 2009 at 12:14 PM, Nicholas Zakas <nzakas at yahoo-inc.com>
wrote:
> Just curious if anyone knows why <img src=""> is the exception in the
> spec, rather than having the same behavior for all elements that
> download resources on page load? As far as I can tell, the spec would
> currently allow self-referencing downloads for the following elements:
>
> * <iframe>
> * <embed>
> * <object>
> * <video>
> * <audio>
> * <source>

As stated. If the other browser vendors are ok with it, I'm ok with
making the empty string mean "don't load" in all these cases. I.e.
treat an empty src/href attribute the same way as an absence of the
attribute (except for <script> which still wouldn't treat it as an
inline script).

/ Jonas
Received on Thursday, 10 December 2009 10:22:59 UTC

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