87946 - focus goes to URLbar when opening new browser via Open Web Location [no form]

Status: VERIFIED DUPLICATE of bug 103758

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

Description

[sairuh (rarely reading bugmail)]

spun off from bug 37638. currently tested using 2001.06.26.0x-branch comm bits
on the three main platforms. not sure if this is already reported [could be, but
my queries today didn't find Just the Right One]...

focus goes to the URLbar when i open new browser via Open Web Location. as with
middle-clicking a link (well, on unix at least :) or entering a url directly in
the Location/URLbar, focus *should* go directly to the web page content area
instead.

i can understand that accel+N or File > New Navigator Window should set focus in
the URLbar. but i don't think this particular situation should act this way.

to observe:
1. bring up the Open Web Location dialog [accel+shift+L, or File > Open Web
Location].
2. select "New Navigator Window" from the droplist.
3. enter a url in the textfield, eg, http://mozilla.org
4. click the Open button [or, hit Enter key].

results:
in the new browser window, observe that the cursor is in the URLbar, blinking at
the end of the url. i'm unable to scroll the page using the keyboard because of
this.

***side note***: if i enter a url of a page which has a form, eg,
http://bugzilla.mozilla.org or http://my.yahoo.com, focus is *not* in the
URLbar. instead, focus [and the cursor] is in the [first] textfield. then i need
i to tab out of the textfield [and any other form elements], after which i can
scroll the page with the keyboard.

Comment 1

[Jesse Ruderman]

Loading http://bugzilla.mozilla.org or http://my.yahoo.com ends up focusing a
text box no matter how you load the page, because those pages contain javascript
to focus the textboxes.

Comment 2

[Brian Ryner (not reading)]

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

Comment 3

[Brian Ryner (not reading)]

This should be fixed now, unless the newly opened window is about:blank.

Comment 4

[sairuh (rarely reading bugmail)]

this is still a problem --but am guessing it because the fix for this was part
of bug 103758, which was backed out.

okay, i'm gonna dup this in favor of 103758, as that one [while filed later]
seems to be more umbrella like.

Comment 5

[sairuh (rarely reading bugmail)]

dup

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

Comment 6

[sairuh (rarely reading bugmail)]

v