W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2009

[whatwg] Inconsistent behavior for empty-string URLs

From: Simon Pieters <simonp@opera.com>
Date: Thu, 17 Dec 2009 22:58:03 +0100
Message-ID: <op.u43ra1q0idj3kv@simon-pieterss-macbook.local>
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
Received on Thursday, 17 December 2009 13:58:03 UTC

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