klui Reporter
	Description • 23 years ago

When I open a link using either the contextual menu or button 2, this new window
doesn't accept keyboard commands. My window manager--WindowMaker 0.62.1--says it
has focus, but it really doesn't. My keyboard focus is configured to follow my
mouse pointer rather than via an explicit mouse click. If I change focus to
another window and back using the mouse, it still does _not_ get the keyboard
focus. Only solution currently is to click within the contents--not even on the
window manager's widgets--of that window.

This is with Mozilla 0.9--I've overridden its user-agent string.

	sairuh (rarely reading bugmail)
	Comment 1 • 23 years ago

aaronl, methinks this is a dupe, or at least definitely related to that "need to
click in order for keyboard commands to work" bug.

	Chris Hiner
	Comment 2 • 23 years ago

related to bug 58250?

	Aaron Leventhal Assignee
	Comment 3 • 23 years ago

This could be a UNIX only problem.

I'm not seeing any different behavior when the context menu is used to open a 
link in a new window.

	basic
	Comment 4 • 23 years ago

dupe of bug 69504?

	Keyser Sose
	Comment 5 • 23 years ago

69504 is a dupe of bug 37638 duping to that.

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

	Aaron Leventhal Assignee
	Comment 6 • 23 years ago

Excuse me?
Someone please explain how this has something to do with whether the URL bar 
gets focused by default.

If it's a dup, it's probably a dup of something listed in the focus meta 
bug 70812

	Keyser Sose
	Comment 7 • 23 years ago

From the other bug:
 Under Linux, when you open a new browser window (including starting
Mozilla up), the URL bar is given focus. This is bad, because it means
that no keyboard navigation shortcuts (such as spacebar to scroll down)
will work until you take a manual step to force Mozilla to put the focus
in the display area.


Thus the dupe ;)

	sairuh (rarely reading bugmail)
	Comment 8 • 23 years ago

mass verification of duplicate bugs: to find all bugspam pertaining to this, set
your search string to "DuplicateBugsBelongInZahadum".

if you think this particular bug is *not* a duplicate, please provide a
compelling reason, as well as check a recent *trunk* build (on the appropriate
platform[s]), before reopening.