W3C home > Mailing lists > Public > public-html@w3.org > August 2007

Re: Dropping <input usemap="">

From: Geoffrey Sneddon <foolistbar@googlemail.com>
Date: Thu, 16 Aug 2007 13:55:58 +0100
Message-Id: <AA87C866-7CC7-4807-84F4-13518F8FE699@googlemail.com>
Cc: public-html@w3.org
To: Robert Burns <rob@robburns.com>

On 16 Aug 2007, at 13:05, Robert Burns wrote:

> On Aug 16, 2007, at 6:19 AM, Philip Taylor wrote:
>> Robert Burns wrote:
>>>>> It doesn't submit form data. We have an <input type-'image'>  
>>>>> that doesn't submit form data (unless the map is nohrefed or  
>>>>> something like that). That doesn't sound like it works as  
>>>>> intended to me.
>>>> It does submit form data, when you click on a part that's not  
>>>> already covered by the client-side image map.
>>> I see I was wrong there, again based on what Lachlan had said. It  
>>> does work in FireFox and Opera as the HTML 4.01 recommendation  
>>> specifies.  And that means that it works when @href is not set on  
>>> the |area| elements (its not just those area not covered by | 
>>> area|). That is the feature we're discussing here. It cannot be  
>>> done without the @usemap attribute.
>> In Firefox/Opera, when you have an <area> with no href, clicking  
>> on that area does nothing at all (unlike when you click on  
>> somewhere not covered by any <area>).
> Well, that's an implementation problem.

Is it? It does what is required in the current spec. What is the  
problem with the implementation issue? Is it due to your use case  
that has never been given to the developers? Firefox/Opera do what  
I'd expect them to under the current spec. The fact that this  
"feature" causes real world sites to break is nothing but a reason to  
exclude it. If it had valid use cases, surely someone pushing the  
limits of HTML4 would've used it as such by now?

- Geoffrey Sneddon
Received on Thursday, 16 August 2007 12:56:10 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:25 UTC