55652 - Ctrl-n doesn't open new window if a text-entry box has cursor

Status: VERIFIED DUPLICATE of bug 55408

(Core :: DOM: UI Events & Focus Handling, defect, P3)

Description

[Jerry Peek]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14-5.0 i686; en-US; m18) Gecko/20001005
BuildID:    2000100521

In M17, and in all Netscape versions I remember before, Alt-n would open a new
browser (Navigator) window.  In the nightly build I downloaded yesterday, that
shortcut has been changed to Ctrl-n.  But the change has broken something else,
I think: typing Ctrl-n while the cursor is in a text-entry box (like the one I'm
typing into now on this Bugzilla form) doesn't open a new window; nothing seems
to happen at all.  I have to click somewhere outside the text-entry box before
Ctrl-n works.

Reproducible: Always
Steps to Reproduce:
1. Click in a text-entry box
2. Press Ctrl-n.

Actual Results:  No new window opens.

Expected Results:  A new Navigator window should open.

Comment 1

[Jerry Peek]

Sorry, this is probably a frequently-reported bug (somehow I missed that...)

Comment 2

[don]

Akkana and Alec discuss this same problem in bug #55408.  It's a known issue due
to the Emacs/Bash-like keyboard shortcuts which are enabled during text input.


*** This bug has been marked as a duplicate of 55408 ***

Comment 3

[sairuh (rarely reading bugmail)]

vrfy dup.

Comment 4

[Boris Zbarsky [:bzbarsky]]

*** Bug 133127 has been marked as a duplicate of this bug. ***

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

I don't agree with this being marked a dup against that bug.

That bug is for switching accelerators, this one is about Ctrl+N not working.

Why do we have to support Emacs-/Bash-shortcuts that are not widely known
anyway, which also causes the product to behave inconsistently (Ctrl+N not
working in textareas)?

Comment 6

[R.K.Aa.]

*** Bug 239991 has been marked as a duplicate of this bug. ***

Comment 7

[Tuukka Tolvanen (sp3000)]

*** Bug 283286 has been marked as a duplicate of this bug. ***