Not a security bug. This appears to be normal windows behavior seen in many other programs including IE.
Any reason why onkeyup? I recommend onkeydown, because: 1) It's early enough to prevent the default action of the event from occurring (which is causing the beep). 2) It also works like that in IE. Note that unfortunately cancelling the default action of the keydown only works in nightly builds of Firefox: http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/ If you want this to work with 1.0 you probably need to handle onkeypress for Mozilla and onkeydown for IE (IE only generates onkeypress for ascii keys). If you return true from the event handler, it means you are consuming the event and thus cancelling the default action. For example: onkeydown="return event.keyCode != 13 || doSomething();" More docs here (although I think the checkbox example is out-dated): http://www.mozilla.org/access/keyboard/tabindex Does that help? I'm 90% sure it will work, but haven't tried it with ALT+ keys.
No response from reporter, marking WFM. Please reopen if Aaron's suggested fix doesn't work for you.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
Summary: Audio Cue when hot key does not exist → No way for page to disable audio cue when browser does not recognize shortcut
You need to log in before you can comment on or make changes to this bug.