Re: TYPE=IMAGE behavior

Patrick McManus <mcmanus@nysernet.org> wrote:
>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">
>
></FORM>
>
>--
>
>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)

	You must be using an old version of Lynx.  What Netscape is doing
is correct.  What Lynx v2.3 or earlier was doing is wrong.  As of v2.4,
Lynx fakes a 0,0 coordinate pair, and will send [&]test_n.x=0&test_n.y=0
TYPE=image is inherently non-GUI client hostile, and nothing but some
work around (and crossing of fingers 8-) can be used for it by non-GUI
clients (or by contemporary GUI clients with image handling turned off).

				Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 MACRIDES@SCI.WFBR.EDU         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================

Received on Thursday, 15 February 1996 11:51:57 UTC