[whatwg] Inconsistent behavior for empty-string URLs
Nicholas Zakas
nzakas at yahoo-inc.com
Thu Dec 17 17:46:27 PST 2009
Yup, I'll take a look this weekend.
-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 Simon Pieters
Sent: Thursday, December 17, 2009 2:44 PM
To: Nicholas Zakas; Jonas Sicking
Cc: Maciej Stachowiak; whatwg at lists.whatwg.org; Aryeh Gregor
Subject: Re: [whatwg] Inconsistent behavior for empty-string URLs
On Thu, 17 Dec 2009 23:20:38 +0100, Nicholas Zakas
<nzakas at yahoo-inc.com>
wrote:
> Simon,
>
> Here's a list for the first four I mentioned:
Nice. Could you test the others as well, and maybe make a table on the
whatwg wiki or something? :-)
Is the result different if the base URL is different from the document's
URL? Is the result different if the value is "#"?
> <img src="">
> IE 8 and earlier: makes a request
> FF 3 and earlier: makes a request
> FF 3.5: does not make a request
> Safari 4 and earlier: makes a request
> Chrome 3 and earlier: makes a request
> Opera 10 and earlier: does not make a request
>
> <link href="">
Is this for rel=stylesheet? Have you tested rel=icon and rel=prefetch (I
think IE needs "shortcut icon" and not all browsers support prefetch)?
> IE 8 and earlier: does not make a request
> FF 3.5 and earlier: makes a request
> Safari 4 and earlier: makes a request
> Chrome 3 and earlier: makes a request
> Opera 10 and earlier: does not make a request
>
> <script src="">
> IE 8 and earlier: does not make a request
> FF 3.5 and earlier: makes a request
> Safari 4 and earlier: makes a request
> Chrome 3 and earlier: makes a request
> Opera 10 and earlier: does not make a request
>
> <iframe src="">
> IE 8 and earlier: does not make a request
> FF 3.5 and earlier: does not make a request
> Safari 4 and earlier: does not make a request
> Chrome 3 and earlier: does not make a request
> Opera 10 and earlier: does not make a request
>
>
> -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 17, 2009 1:58 PM
> To: Jonas Sicking
> Cc: Nicholas Zakas; Maciej Stachowiak; whatwg at lists.whatwg.org; Aryeh
> Gregor
> Subject: Re: [whatwg] Inconsistent behavior for empty-string URLs
>
> On Wed, 16 Dec 2009 17:21:01 +0100, Jonas Sicking <jonas at sicking.cc>
> wrote:
>
>>>> So the specific list would then be:
>>>>
>>>> <img>
>>>> <link>
>>>
>>> I think only icon, prefetch and stylesheet links.
>>>
>>> The following element defines two links, one of which would be
> ignored:
>>>
>>> <link rel="icon index" href>
>>
>> Sounds good.
>>
>>>> <script>
>>>> <iframe>
>>>> <video>
>>>
>>> Including poster?
>>
>> Yes. Good catch.
>>
>>>> <audio>
>>>> <object>
>>>> <embed>
>>>> <source>
>>>> <input type=image>
>>>
>>> <command icon>?
>>> <html manifest>?
>>> <applet code>? (Maybe not, since it's more of a parameter to the
Java
>>> plugin.)
>>> <frame src>?
>>
>> I don't really feel strongly about <applet> given that it's
>> deprecated. But sounds good.
>
> I asked Philip to provide some data about pages using empty attributes
> for
> these:
>
> <Philip`> zcorpan:
http://philip.html5.org/data/empty-url-attributes.txt
> <Philip`> zcorpan:
> http://philip.html5.org/data/empty-url-link-attributes.txt
>
>
> I have not looked at these yet, but it would probably be good to do so
> before changing things, so we have an idea what the compat impact is.
It
>
> would also be good to document what browsers do today for all of
these.
>
--
Simon Pieters
Opera Software
More information about the whatwg
mailing list