[Bug 12687] 4.10.22.4 Constructing the form data set - for input type image

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12687

--- Comment #14 from Stefan de Konink <stefan@konink.de> 2011-08-12 23:17:45 UTC ---
(In reply to comment #13)
> Is there a testcase demonstrating the various behaviours here? Is there any
> documentation on which sites this behaviour breaks? Which browsers had which
> behaviour? I'd like to study this further.

I can only comment on the fact that after our CMS broken on 'mandatory' Firefox
upgrade, I went searching in the bugtracker of Mozilla and found a not of noise
on the why this change was pushed trough.

Historically I know that the behavior this change request would like to achieve
was supported on Firefox < 4. And is still supported in Safari and Chrome. I am
certain it never worked in Internet Explorer. I have no data on Opera.


The rationale for us using the image submit (historically) was presenting the
user with several graphical panes that could be choosen from, renderings of a
screen. Analogue to a submit button having text. Now you could argue: "but why
don't you use CSS to set a background image on a submit button". This was
indeed the solution to get crossbrowser support.

But reading the documentation on W3Schools:
"image    Defines an image as a submit button"

My point being: functionality wise nothing is lost by moving to
type=submit/background-image. But are we really going to define a standard that
explicitly makes one exception on name/value passing?

I'm not puting the more radical: "why not remove the 'img' tag, because you
could use a div tag with background-image", argument here. Because it is
clearly a no brainer the functionality is already in place, only an explicit
exception is made.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 12 August 2011 23:17:51 UTC