It looks like you'll have to find another way, like making your page number part of the name, such as

<INPUT type="image" name="page23" src="...">
[download]

A grep through all params with a name matching /^page(\d+)\.x$/ will then find your page number.

($param) = grep /^page\d+\.x$/, $cgi->param;
[download]

($page) = map /^page(\d+)\.x$/, $cgi->param;
[download]

That doesn't look half bad to me.

Try replacing the action on the form with a simple CGI parameter dumper like this:

#!/home/crossda/perl/bin/perl

use strict;
use warnings;

use CGI ':cgi';

print header(-type => 'text/plain');

foreach (param) {
  print "$_ : ", param($_), "\n";
}
[download]

You'll see that Firefox sends parameters called "page.x", "page.y" and "page". IE doesn't send the "page".

You'd need to check the specs, but I suspect that IE is doing all it's supposed to do. The extra parameter from Firefox is useful but (I think) non-standard.

Even simpler (= less work), make the form use a GET (don't specify a method for the form) and look at the URL after you submit.

The way I got around it was (as has been suggested) to assign individual names to each INPUT control. In my case, I was using arrow images as sorting buttons. The code to render the HTML was a little like so:

print qq(<input type="image" name="sort:$field:asc" src="$image_dir/do
+wn.png">);
[download]

I had about 20 of these little "sorting" buttons on my page, so when it came to working out which one had been clicked (if any), I did this:

my ($sort_string) = grep { $_ =~ /^sort/ } @params;
my ($sort_field, $sort_dir)
    = defined($sort_string)
    ? $sort_string =~ /^sort:(\w+):(\w+)/
    : qw(avin desc);
[download]

The above worked fine in both IE and Firefox.

Hope this helps,
Darren :)

This one's very simple, yet clever approach. I'll implement this in my subsequent routine when necessary.

<form action="/blabla" method="post">
  <input type="hidden" name="mypage" id="mypage" value=""  />
  <input type="image" name="page" value="1" src="/static/images/suchen
+.gif" onclick="document.getElementById('mypage').value='1';" />
  <input type="image" name="page" value="2" src="/static/images/suchen
+.gif" onclick="document.getElementById('mypage').value='2';" />
  ...
</form>
[download]

$page = $cgi->param('page') || $cgi->param('mypage') || 1;
[download]

It's a problem with IE

I think that's overstating the case. IE is doing exactly what it should be doing. Firefox has added some new and useful behaviour. But it's non-standard* and IE can't be expected to support it.

* Or, at least, I can't find any standards that mandate the Firefox behaviour.

--
<http://dave.org.uk>

"The first rule of Perl club is you do not talk about Perl club."
-- Chip Salzenberg

A form data set is a sequence of control-name/current-value pairs constructed from successful controls and if a form contains more than one submit button, only the activated submit button is successful while image creates a graphical submit button.

It does say: 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.

... but I can't see anywhere that it says the normal behaviour of other form controls (submitting the name/value pair) doesn't apply as well.

Thanks for your inputs guys! I made it to work using this workaround:

<TD>
  <INPUT type="hidden" name="page">
</TD>
<TD>
  <A href="javascript:do_Submit(1)"><IMG src="page1.gif" ...></A>
  <A href="javascript:do_Submit(2)"><IMG src="page2.gif" ...></A>
  <A href="javascript:do_Submit(3)"><IMG src="page3.gif" ...></A>
  <A href="javascript:do_Submit(4)"><IMG src="page4.gif" ...></A>

  ...

  <A href="javascript:do_Submit(50)"><IMG src="page50.gif" ...></A>
</TD>
[download]

The on the javascript:

function do_Submit(page) {
  var page;
  document.forms[0].page.value = page;
  document.forms[0].submit();
}
[download]

I also confirmed that this wasn't supported in the HTML specs. I just assumed too much when I made the code. But I wasn't able to catch it soon enough since I am always using Firefox

<button name="page" type="submit" value="1"><img ...></button>
<button name="page" type="submit" value="2"><img ...></button>
<button name="page" type="submit" value="3"><img ...></button>
...
<button name="page" type="submit" value="50"><img ...></button>
[download]

Another bug in IE causes <button> elements to be submitted with the text content the element instead of the value attribute.

I could be wrong, but I seem to recall they IE also treats all <button>s as successful controls, even if they are unclicked submit buttons.

Try closing the INPUT tag, eg:

<INPUT type="image" name="page" value="1" />
[download]

--Darren

The OP is using HTML, not XHTML (they said "HTML" and XHTML doesn't have an INPUT element (it does have an input element though)).

So the element is already closed and adding a "/" will effectively make it mean <INPUT type="image" name="page" value="1">> thanks to SGML rules that most browsers don't implement (Appendix C of XHTML 1.0 exploits this common browser bug).