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

Re: Dropping <input usemap="">

From: Robert Burns <rob@robburns.com>
Date: Thu, 16 Aug 2007 10:34:43 -0500
Message-Id: <0161DC89-91C5-4A53-8A2F-B0A507E58799@robburns.com>
Cc: public-html <public-html@w3.org>
To: Philip Taylor <philip@zaynar.demon.co.uk>

On Aug 16, 2007, at 10:09 AM, Philip Taylor wrote:

> Robert Burns wrote:
>> The difference between <input usemap> and <img usemap> is the same  
>> as the difference between <input type='image'> and <img>. [...]
>> What would YOU say are the differences between THESE: <input  
>> type="image"> and <img>?
> When you click on an <img>, nothing happens - it's just a non- 
> interactive image. When you click on an <input type=image>, the  
> input's form is submitted with the mouse coordinates added as 'x'  
> and 'y' - it's an image and a server-side image map and a form- 
> submission button.

But an <input> has uses outside of forms. What about the difference  
between an <img>  and <input> without a <dorm>. Then they both can  
capture mousse events right? Can they both respond to click events?  
Are they basically the same when the <input> is not in a form?

> <input type=image> is closer to <a href><img ismap></a> - in that  
> case, both are server-side image maps, and the difference is that  
> <img ismap> does a GET request with just the x and y arguments,  
> while <input type=image> does a form submission with all the form's  
> other input values in addition to the new x and y.

OK, that makes sense. However, without the form, are there no  
differences between the two? I imagine, a <input type='imate'> can  
also be associated with a label even though <img> cannot. Are there  
any other differences? Are there extra events automatically  
associated with a click() or an activate() event on an <input  
type='image'> compared to an <img>?

> So the differences with <img ismap> are "one can only do GET" and  
> "one submits all the form's other input values too", and I can't  
> see any way for those differences to apply to client-side image  
> maps (i.e. usemap) since client-side image maps are never  
> associated with forms.

However, client-side image maps could be associated with forms if  
HTML5 specified the use of <input usemap> more fully.. Don't Opera  
and Firefox already support client-side image maps with forms using  
<input usemap>?

Take care,
Received on Thursday, 16 August 2007 15:34:52 UTC

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