Subj : Re: SELECT onChange doesn't work with keypresses
To   : netscape.public.mozilla.jseng,netscape.public.mozilla.dom
From : Brendan Eich <brendan@meer.net>
Date : Wed Feb 05 2003 09:24 pm

Sam Hulick wrote:

>I know this is a WONTFIX, because W3C docs
>

DOM docs, you mean -- which should suggest to you that you're posting to 
the wrong newsgroup.  I'm cross-posting with followup-to: set.

/be

> say that onChange will be
>triggered only when the SELECT loses focus.  But this is kind of
>ridiculous.. What about situations where you really NEED to do something
>whenever the SELECT value is changed, via mouseclicks or keypresses?
>Currently, in 1.2.1, the onChange is triggered immediately by mouseclicks,
>no need for the element to lose focus.  But keypresses (up/down) do nothing
>at all until the item has no focus.  I've remedied this by putting funcs in
>for two events to cover both bases:
>
>  <select name="bob" onChange="do_it()" onKeyUp="do_it()">
>
>But this is kind of hacky, and in IE, the do_it() fires twice.  I suppose I
>could hack it more and put in a check in the do_it() function that sees if
>the value really changed.  If not, don't do anything.  But this shouldn't be
>necessary.
>
>Personally, I find the W3C's decision in this matter to be not very well
>thought out.  One can't simply make up a rule about how an event should work
>without first looking around in the world to see how people are currently
>using it, and how it will affect them.
>
>--
>Sam Hulick
>Designer/Developer
>HitNet
>http://www.hitnet.com/
>
>
>
>  
>

.