Rahul Akolkar wrote:
In a multiple , selectName.selectedIndex will always be the
index of the *first* selection, if there are one or more (or -1 if
there are none).
Cool, that's what I thought but wasn't sure, you saved me from having to
test it :)
I think Mike has the answer I wa about to g
Thank you, Rahul. This *is* the problem.
Much regards (and much better sleep this weekend!)...
Mike
Rahul Akolkar wrote:
On 12/9/05, Mike Darretta <[EMAIL PROTECTED]> wrote:
I thought I had licked this problem - but it only works with Firefox!
I have an tag that, when a user selects an opt
On 12/9/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> What are you actually trying to send? The selected value or the index
> of the selected item? I also note you have multiple="true"... so you
> expect that more than one can be selected? I'm not sure if that has a
> bearing on the selecte
On 12/9/05, Mike Darretta <[EMAIL PROTECTED]> wrote:
> I thought I had licked this problem - but it only works with Firefox!
>
> I have an tag that, when a user selects an option, a
> submit() is forced through a javascript call.
>
> The JSP code is:
>
> ...
> onclick="handleCl
You're right - the multiple="true" was wrong, but that was essentially
ignored since I am capturing the "onclick" event. What I want to send is
the index to use in extracting the appropriate info from the underlying
collection.
Anyhow, what I am wanting to do is capture the selected index, the
What are you actually trying to send? The selected value or the index
of the selected item? I also note you have multiple="true"... so you
expect that more than one can be selected? I'm not sure if that has a
bearing on the selectedIndex (I could see where it might), and even if
it does, the
6 matches
Mail list logo
