W3C home > Mailing lists > Public > www-html@w3.org > February 1996

TYPE=IMAGE behavior

From: Patrick McManus <mcmanus@nysernet.org>
Date: Thu, 15 Feb 1996 11:05:48 -0500 (EST)
Message-Id: <199602151605.LAA18493@pat.nyser.net>
To: www-html@w3.org
Folks, I need a little clarification on the IMAGE type of a form
input. Netscape doesn't seem to exhibit the behavior I'd expect, and I
want to confirm that it is them, not me.

<FORM action=".." ENCTYPE="...">

<INPUT TYPE=IMAGE NAME="test_n" VALUE="test_v" SRC="/something.gif">



Okay, now if the Netscape user clicks on rendered image the inputs
passed to the cgi look something like:

test_n.x = ##
test_n.y = ##

but take a text browser (lynx!) and selecting that button yeilds:

test_n = test_v

Which is exactly what I would expect from lynx, I would expect all 3
from Netscape.. The spec says:

An INPUT element with `TYPE=IMAGE' specifies an image resource to
display, and allows input of two form fields: the x and y coordinate
of a pixel chosen from the image. The names of the fields are the name
of the field with `.x' and `.y' appended. `TYPE=IMAGE' implies
`TYPE=SUBMIT' processing; that is, when a pixel is chosen, the form as
a whole is submitted.


Because of the "implied type=submit processing" I expect to see the
name=value pair also but I admit to the ambiguity..

anyone with a definitive answer?

(please do not suggest work arounds, I've already done that. I want to
know what I should expect and if it is a bug or compliant behavior wrt
HTML 2.0)


Patrick R. McManus	NYSERNet, Inc.		Information Services
http://pat.nyser.net/~mcmanus			Software Development
mcmanus@nysernet.org	'Prince of Pollywood'	Standards, today!
*** - You Kill Nostalgia, Xenophobic Fears. It's Now or Neverland. - ***
Received on Thursday, 15 February 1996 11:05:56 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 30 April 2020 16:20:17 UTC