Closed Bug 100454 Opened 23 years ago Closed 23 years ago

intermittent focus on browser address bar

Categories

(SeaMonkey :: General, defect)

PowerPC
Mac System 9.x
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 76621

People

(Reporter: phoyt, Assigned: mpt)

Details

Open a new browser window with a start page of some sort. Start typing a URL--don't 
click anywhere with the mouse, just start typing. about half-way though, you will be 
interrupted as the focus is lost. You may need a fairly slow mac computer to notice -- I'm 
on a 233 mhz powerbook g3.

Now set Mozilla to open a blank page in preferences. Open a new window. Try to type in 
a url without first clicking anywhere with the mouse. Nothing at all happens.

The correct behaviour for a browser is that you should immediately be given focus on 
the address bar without hesitation. 

Try, for comparison, starting Sherlock 2 on a slow-ish mac. Start typing before the 
application even appears on the screen. You will notice that all the text you have typed 
since the beginning is displayed in the search text field.
Reporter, I'm afraid neither of your scenarios cause me the problem you describe using 
Mac/2001091311 (0.9.4). What Build ID are you using?
I'm using the same. In fact the only time I get the right focus is at *start-up*
when I have the default set to open a blank page. I can't think of any other
variables that might be involved.
This might be a duplicate of bug 76621.  phoyt@macbox.com, if you continue 
typing after the location bar loses focus and then open the sidebar, do your 
missing letters end up in the sidebar?
You're right, it does end up in the sidebar ... even though the sidebar is 
closed.
Marking duplicate per Jesse and Philip.

*** This bug has been marked as a duplicate of 76621 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Component: User Interface Design → Browser-General
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.