107932 - When launched, blinking cursor should allow immediate URL entry in Location field when default page is about:blank

Status: VERIFIED DUPLICATE of bug 76621

(SeaMonkey :: UI Design, defect)

Description

[Adam Kramer]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.5) Gecko/20011011
BuildID:    2001101117

When Mozilla is launched, a new browser window opens with nothing in it, if this
has been selected in the preferences. The cursor should default to being in the
Location field as soon as the browser window opens. Currently, it seems to spend
just a moment in the Location field, but then disappears, leaving a "cursor
shadow," which does not blink and does not allow text entry.

Reproducible: Always
Steps to Reproduce:
1. Launch Mozilla under MacOS, with Navigator set to open a blank page on startup
2. Note that there appears to be a cursor in the Location field before you click
into the Location field, but that it does not blink because this field does not
actually have focus.
3. Attempt to type in the URL you wish to access.
4. Fail.

Actual Results:  As per step 4, I failed to enter my URL without first clicking
into the Location field.

Expected Results:  Allowing user to type a URL in immediately after opening the
blank page, just after Mozilla is launched.

Comment 1

[sairuh (rarely reading bugmail)]

clarifying summary. however, this is prolly a dup...

if the default page is anything other than about:blank, however, focus should
certainly be in the web page content, not the URLbar --see bug 103758.

Comment 2

[Jesse Ruderman]

This is probably the search sidebar stealing focus (bug 76621).  If you open 
the sidebar after opening a browser window, you should see focus in the textbox 
in the sidebar panel.  Closing the sidebar completely (using F9), rather than 
collapsing it, should let you work around this bug.

Comment 3

[Adam Kramer]

[e-mail] is indeed correct; the problem goes away if the sidebar is
closed completely.

Comment 4

[Jesse Ruderman]

Let's mark this as a dup of 76621, since the bug in Mozilla hasn't really been 
fixed...

Comment 5

[Jesse Ruderman]

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

Comment 6

[sairuh (rarely reading bugmail)]

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.