Closed Bug 278261 Opened 20 years ago Closed 17 years ago

Cannot navigate by typing in address bar

Categories

(Firefox :: Address Bar, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jcaesar, Unassigned)

Details

(Whiteboard: CLOSEME - 06/20)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050113 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050113 Firefox/1.0+

Launch several blank windows. Cannot navigate from address bar using:
1) search terms
2) partial URLs (www.whaterever.com)
3) full URLs (http://www.whatever.com)
4) IP addresses (123.123.1.123)
5) auto-complete selections

with yesterday's build, I could not navigate using the bookmarks, either.

Reproducible: Sometimes

Steps to Reproduce:
1. Login to Windows
2. Launch 4 browsers (from tray button, blank homepage)
3. Try to surf.

Actual Results:  
All 4 widows were useless for surfing.
A fifth window was launched from another program (g-mail notifier) and worked
perfectly. Other windows were still dead.

Expected Results:  
worked.

Seems to only happen after login.
Does not happen after ALL windows are closed and opened again.
Did NOT try to launch a new blank window after G-mail Notifier launched its
targeted window.
Bookmarks used to work when this happened.


I'm seeing similar behavior on Mac OS X (10.3.8)

On startup only the "firefox" menu item displays keyboard inoprative, mouse
navigation ok. I was also unable to type in this text area from firefox and had
to load mozilla (1.8a1) in order to add this comment. 

If I close the initial window the full menu bar displays some of the time but
the keyboard is still inoprative most of the time on opening a new window, the
behavior here is erratic & i've not been able to characterize it.

I'm able to mouse select text in the address/location bar but delete etc have no
effect. 
I had the same problem, but the window is still useful due to bookmarks still
working and the google search box working. (using alpha 2)

Always reproduceable for me. Simply launching a window from the latest nightly
got me this problem
Seeing this on Linux, build 2005-07-09-trunk.
Seems to me that there are no such problems with today's nightly on windows:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050710
Firefox/1.0+
Mass edit: Changing QA to default QA Contact
QA Contact: davidpjames → password.manager
Mass edit: Setting correct QA for location bar/autocomplete. My bad. I forgot I had once been Autocomplete QA too. Hmm, why can't I just set the QA of bugs to the default QA of the component in a mass edit rather than having to do it manually...?
QA Contact: password.manager → location.bar
I'm having the same problem with Firefox 2.0.1 for the Mac - latest version. I saw the same problem in Firefox 2.0. It was there in 1.5, but after a few minutes, it went away. I'm running 10.3.9, and after Firefox has been open for an hour or so, I can't type anything in the address bar. I have to open a new window, and the new window has the same problem after only a few minutes. This results in a lot of open windows, which is frustrating and defeats the entire purpose of tabs.
Assignee: bugs → nobody
WFM with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/2007051502 Firefox/2.0.0.4.

Reporter (or anyone else that saw this problem), can you verify that you're still seeing this problem with 1) a clean profile and 2) the latest version of Firefox?

http://kb.mozillazine.org/Profile_Manager
I'd also ask... do any one of you have proxies or firewalls setup? A poor router could cause an issue like this.
Whiteboard: CLOSEME - 06/20
Resolving as WORKSFORME since this works for me. If you're still able to reproduce this with Firefox 2.0.0.4 and a new profile, please comment in this bug with full details that answer the questions in comments 8 and 9.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.