Really, at this point I think the best course of action for Sony is ritual suicide.

eta:

"You know, in certain older civilized cultures, when a major corporation has failed as badly as you...."

Although I can't get the link (where this info came from) to load.

Here's one reference: [link]

I knew that was coming, tommy -- I was too lazy to check the wording myself!

I knew that was coming, tommy -- I was too lazy to check the wording myself!

I pulled the wording from memory (pretty sure it's close). Think of all the time I'll save by not having to google Serenity quotes, and all I had to do was see the movie seven times in the theater.

In a web page, why does the javascript onblur event get fired for a select combobox when I hit the 'Esc' key after typing into the select combobox?

In a web page, why does the javascript onblur event get fired for a select combobox when I hit the 'Esc' key after typing into the select combobox?

The onblur event fires when a control loses focus. Hitting the Esc key causes it to lose focus (IIRC).

Well, that's... dumb counterintuitive.

Huh. The onChange event fires too. That's less counterintuitive, but still not what I want.

OK, so I need to use the onKeyDown or onKeyPress events to set a flag when the user hits escape, which will tell the functions that the onChange and onBlur events call to do nothing for that case. Then I need to reset the flag back. It's that setting the flag back part that bugs me - I can't think of a non-kludgey way to do it. And it needs to be set back after all the events are done firing.

If memory serves, the events are fired in order, so you could try setting the flag back in the last event. I can't find a definitive listing of the event order offhand, but I'm sure a little experimenting will tell you where to put it.

I'm thinking something like this at the top of the last event's function:

if ($flag) { $flag = 0; return; }

One other thing you might try from the onkeypress event's function is to set the subsequent events to null:

document.[formname].[controlname].onblur = null; document.[formname].[controlname].onchange = null;

I'm not sure if that'll kill those events for good, or for just that execution, so play around with it.

Not sure if I'm being helpful, but maybe it'll give you some ideas.

Thanks Eddie.

My boss and I messed around with it, and he decided that the whole thing was just too complicated to mess around with just to fix a tiny bug. (There's pages of code associated with just that one select combobox.)

My Powerbook's Bluetooth is erratic. As in, not there when I need it. Last time it took a lot of rebooting to get it to act right again.

Where does one start troubleshooting that? With support, or is there anything I can do myself?