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:43 -0800
Message-ID: <4E45EC6AD219FD47AD1BC06E4EE3845D0420D0B3@SNV-EXVS09.ds.corp.yahoo.com>
I'd be happy to make the compromise that this applies to markup but not
to JavaScript APIs. 

It's the "automatic download" that makes this problematic, as it
silently doubles the number of requests to the server, which as I've
said in previous emails, is a huge problem for high-volume sites. Opera
already doesn't make a request in all of these cases, so I'm guessing
that Web Workers is an exception?

Commander Lock: "Damnit Morpheus, not everyone believes what you
Morpheus: "My beliefs do not require them to."

-----Original Message-----
From: Anne van Kesteren [mailto:annevk@opera.com] 
Sent: Thursday, December 10, 2009 1:56 AM
To: Nicholas Zakas; Simon Pieters; Aryeh Gregor
Cc: whatwg at lists.whatwg.org
Subject: Re: [whatwg] Inconsistent behavior for empty-string URLs

On Wed, 09 Dec 2009 21:14:00 +0100, Nicholas Zakas
<nzakas at yahoo-inc.com>  
> Can the self-reference <img> exception become the rule and apply to
> of these tags the same way?

If we'd also apply it to APIs that would be annoying actually. We have a

bunch of Web Workers tests that rely on this working fine.

What is wrong with having this work as is?

Anne van Kesteren
Received on Thursday, 10 December 2009 10:22:43 UTC

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