Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!eternal-september.org!feeder.eternal-september.org!newsfeed101.telia.com!starscream.dk.telia.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Mel Smith" <med_cutout_syntel@aol.com>
Newsgroups: comp.lang.javascript
Subject: Re: Accessing a <select> <option> ?
Date: Tue, 22 May 2012 20:26:11 -0600
Lines: 27
Message-ID: <a2306aFqreU1@mid.individual.net>
References: <a2273uFft7U1@mid.individual.net> <jpgtps$v0t$1@dont-email.me> <a22dkbF24fU1@mid.individual.net>
X-Trace: individual.net s26O3Z7TozuTHCE2FlTqNAewylafITwVXaegaxPEoJWlEt+s9ZdOLeKs8vKyz62v6i
Cancel-Lock: sha1:bwB0p3U0mZy5aJQcewkeCltJq2M=
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-RFC2646: Format=Flowed; Response
Xref: csiph.com comp.lang.javascript:14106

Matt said:

"Mel Smith" <med_cutout_syntel@aol.com> wrote in message 
news:a22dkbF24fU1@mid.individual.net...
> Matt said:
> [snip]
>
>> Yes; you are correct in noting that the `click` event does
>> not work well with option elements. Perhaps, as has been
>> suggested in various threads before, you could add a `blur`
>> and/or `focus` event handler to the select element and track
>> "changes" that way. The first selected option (presence of
>> the `multiple` boolean attribute was not specified) can be
>> retrieved via the `selectedIndex`[1] property of the
>> `HTMLSelectElement`interface.
>>

Matt:

    I've included the <select> element and the selectedIndex into my page, 
and now things work great !

Thank you.

-Mel Smith