- From: <bugzilla@jessica.w3.org>
- Date: Wed, 18 May 2011 16:47:47 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12687 --- Comment #5 from Luca Tomat <luca.tomat@gmail.com> 2011-05-18 16:47:46 UTC --- (In reply to comment #4) > > and so did intranet developers > > I explicitly said that I understand how intranet issues can arise. You claimed > there are broken _internet_ sites. I'd like to understand your basis for this > claim. The forget about the internet sites and lets think about intranet sites and in general about the logic in this algorithm. > > I don't see any logic into the current implementation > > It's what IE does and what matches the HTML4 spec most closely. What is the logic about "It's what IE does"? Can you tell me where in the HTML4 spec it says that the name-value pair should not be sent? How is IE implementation better than, say, Firefox 3.6 or Google Chrome? Also, what if the user does not use the mouse? Wouldn't it be more logic (especially in the keyboard-only case) to also send the name-value pair (as for other input elements) since most sites (intranet and not) use the image input element not as an "imagemap" (where X,Y coordinates are necessary) but just as a graphical representation of a button (where X,Y coordinates just do not matter at all)? IMO the current implementation is just illogic. There is no reason i can see why the image input element should behave differently than other input elements. Of course i can be wrong and there is a logic reason behind it beside "IE works like this"... but if there is i would like to know it. -- 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 Wednesday, 18 May 2011 16:47:48 UTC