Open
Bug 337172
Opened 19 years ago
Updated 2 years ago
Can't cancel ctrl+tab on keydown
Categories
(Core :: DOM: Events, defect, P5)
Tracking
()
UNCONFIRMED
People
(Reporter: danswer, Unassigned)
Details
Attachments
(1 file)
1.89 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2
If I set a text box / textarea with a keydown listener and want to cancel ctrl+tab, it is not cancelled. I have to wait around for the keypress event to do it. This doesn't seem nice from an architectural point of view.
Use case: I'm writing a keyboard remapper for textareas and when I get keyboard entry, if it's to be remapped, I supply the new action in the keydown event, and if such action is supplied, the original keydown event is cancelled. This architecture has been working fine, except for ctrl+tab I should have to go into a special mode just to eat the next keypress event. This strikes me as awkward.
Perhaps there are other such key combinations requiring keyPress cancellation, but I don't know of any so that is the other reason I find this so peculiar.
Csaba Gabor from Vienna
Reproducible: Always
Steps to Reproduce:
See the attachment. You can set it either to cancel the ctrl+tab keydown or keypress event. Just make sure there is another tab in the window and that focus is in the textbox.
Expected Results:
I expect that cancelling the keydown event on ctrl+tab will cancel the default action of switching to another tab.
Csaba Gabor from Vienna
Reporter | ||
Comment 1•19 years ago
|
||
Updated•15 years ago
|
Assignee: events → nobody
QA Contact: ian → events
Comment 2•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•