Two input type='IMAGE' with the same name - need help on form processing

Spectro

Hello.

I'm sutck on form processing.

The case:
I need about 2-3 buttons on my form that will define the operation passed to the processing form. But these buttons need to be IMAGE type.

I tried the following:

I expected my form would get one of the 3 values on variable $operation ('include','update' or 'delete'). But I'm getting nothing on it.
I searched the <input> tag and saw that there wasn't a 'value' parameter assinged to 'input type image'.

Anyone can help?
Thx in adv.

acey99

Yes.

Each button actually get's it's x/y values as well.

thusly $operation_x and $operation_y

I'd also reccommend using different names on each operation1, 2 , 3 ...

in Perl it's $operation.x & $operation.y after parsing.

the value="" actually doesn't matter, you can set that after submit.

beware: the x/y values can differ from browsers (IE/Netscape ....) to Operating systems (Window, Max, Linux) to Various screen sizes & resolutions (800x600, 1024x768 ...)

MrAlaska

The 'value' attribute for an image input is optional. Somebody told me somewhere they had a browser that could read the value attribute of an image input, but I can't remember who or where it was.

To further comment on what acey99 said:

http://www.w3.org/TR/REC-html40/interact/forms.html

image
Creates a graphical submit button. The value of the src attribute specifies the URI of the image that will decorate the button. For accessibility reasons, authors should provide alternate text for the image via the alt attribute.
When a pointing device is used to click on the image, the form is submitted and the click coordinates passed to the server. The x value is measured in pixels from the left of the image, and the y value in pixels from the top of the image. The submitted data includes name.x=x-value and name.y=y-value where "name" is the value of the name attribute, and x-value and y-value are the x and y coordinate values, respectively.

If the server takes different actions depending on the location clicked, users of non-graphical browsers will be disadvantaged. For this reason, authors should consider alternate approaches:

Use multiple submit buttons (each with its own image) in place of a single graphical submit button. Authors may use style sheets to control the positioning of these buttons.
Use a client-side image map together with scripting.

Spectro

These answers were really helpful. Thanks.
I realized that by using image input types would not fit by needings the way I was figuring.

So I kept the images, created a hidden input type named 'operation' and defined the image's OnClick with something like that: "javascript: document.forms[0].image_name.value = 'update'"

Thus, I have a variable $operation valued as 'update' or 'delete' depending on the image was clicked.

A dirty solution, but works :p