in reply to Re: Passing 'SELECT MULTIPLE' parameters and CGI
in thread Passing 'SELECT MULTIPLE' parameters and CGI

Thanks guys, but I'm not even getting the value in 'runs' to worry about changing the query part. I will fix that up (thank you) as soon as I manage to actually pass multiple values to the called program.
Incidentally I do have warnings and strict, I just pasted snippets.

The weird thing is I have 

my $selectline = '<SELECT name="runs" MULTIPLE size="15" id="runs">';
print $selectline;

[download]

Running it in debug, that's what appears to be printed, yet when I look at the source on IE8 it has it as

<select name="runs" id="runs" size="15" multiple="multiple">

and firefox has it as

<select id="runs" size="15" multiple="" name="runs">

In both instances it seems to have changed the order and set MULTIPLE to either "" or "multiple".
I'm wondering if it's simply not picking up the 'multiple' setting as it correctly passes down individually selected items but not multiple selections,

Replies are listed 'Best First'.
Re^3: Passing 'SELECT MULTIPLE' parameters and CGI
by ikegami (Patriarch) on Aug 17, 2010 at 16:56 UTC

    In both instances it seems to have changed the order and set MULTIPLE to either "" or "multiple".

    The value of multiple doesn't matter, just the presence or absence of the attribute.

[reply]

      I think this is only true for HTML, but XHTML insists on having a value for multiple, and it must be multiple. The same applies to checked and other "no-value" attributes.

      Alexander

      --
      Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
[reply]
[d/l]
[select]

        The only difference is that XML (and thus XHTML) requires that you specify a value if you specify the attribute. XHTML does not impose any extra requirements on what the value is.

        It's must either be multiple="multiple" in both or in neither.

[reply]
[d/l]

In Section Seekers of Perl Wisdom