[whatwg] Inconsistent behavior for empty-string URLs

[Nicholas Zakas]

It seems that thusfar, Jonas from Mozilla is open to this change. Is
there anyone from Opera or WebKit that would like to chime in either in
favor or opposition?

Thanks.

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

-----Original Message-----
From: whatwg-bounces at lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Nicholas Zakas
Sent: Friday, December 11, 2009 10:15 AM
To: Simon Pieters; Anne van Kesteren; Aryeh Gregor
Cc: whatwg at lists.whatwg.org
Subject: Re: [whatwg] Inconsistent behavior for empty-string URLs

I agree, automatic downloads are the real issue. <a href=""> is fine
because a user must initiate the action (and thus generate a "real"
pageview).

I'd think that the behavior should be the same in CSS and SVG for
resources that are automatically downloaded.

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

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

On Thu, 10 Dec 2009 19:22:43 +0100, Nicholas Zakas
<nzakas at yahoo-inc.com>  
wrote:

> I'd be happy to make the compromise that this applies to markup but
not
> to JavaScript APIs.

I think it shouldn't apply to markup that doesn't download things  
automatically; in particular <a href=""> should work.

What about URLs in CSS and SVG?

-- 
Simon Pieters
Opera Software