610005 - POST variables incomplete for input type image

Status: RESOLVED DUPLICATE of bug 583211

(Core :: General, defect)

Description

[energizamx]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5) Gecko/2008032600 SUSE/2.9.95-25.1 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5) Gecko/2008032600 SUSE/2.9.95-25.1 Firefox/3.0b5

Normally, the <input type="image" name="name" value="val"> control creates POST variables name_x and name_y holding the coordinates where the mouse clicked on the image.  Also the post variable "name" is sent with the value "val"

This 3.0b5 runs ok with it, but the 4.0 beta with HTML 5 only produces the name_x and name_y, but nothing abut the "name" with value "val".  This  makes my software to not detect the pressing of the image by the "name" post variable, only through the image_x and image_y (as the coordinates are 0 when something other than the image activated the posting of the form)

Reproducible: Always

Steps to Reproduce:
1.In PHP, Make a <form> with an input controle of type "image" and with some value="something".  I named the control "buscar" and gave it a value="Buscar" (first "B" in capital).
2.Push the image and let the PHP routine to print_r the $_POST array.
3.Try the samething in previous versions of firefox
Actual Results:  
    [buscarh_x] => 1
    [buscarh_y] => 44


Expected Results:  
    [buscarh_x] => 1
    [buscarh_y] => 44
    [buscarh] => Buscar


That's all, the problem is easy to reproduce

Comment 1

[energizamx]

errata on text: "...my software to not detect the pressing of the image by the "name" post variable, only through the image_x and image_y ..."

should say: "...my software to not detect the pressing of the image by the 'name' post variable, only the 'name_x' and 'name_y' are received ..."

Comment 2

[Nickolay_Ponomarev]

A testcase would be welcome here. Also, do you have a more specific regression range? Did it work in 3.6.x for you?

Comment 3

[Josh Matthews [:jdm]]

This is an intentional change to line up with the HTML5 spec and other browsers.  See bug 547165 for more information.