>>Erik,
>>
>>What you say is true, ONLY if the combo is a drop down list. If it is a drop down combo then interactivechange fires with each keystroke.
>
>Which, IMHO it should. If I want something to run everytime the user changes the value of the box, then this is the place. But as you said, it depends on what you are doing.
>
>BTW what the heck are you doing at your computer at this hour on a saturday night? :)

Erik,

Talking to you :-).

That's the real issue here. What does the design call for. If it is a reaction to the selected item changing, that's one thing. If it is a reaction to keystrokes, that's another.

My point in saying the when is the event for reacting to the selected item being changed is simply based on the fact that When is the event that fires when the selected item changes. So does interactivechange, but it also fires at other times (potentially) during the process. So the bottom line is what is it supposed to do and when is it supposed to do it? The answer dictates which event to use.