Closed Bug 437364 Opened 17 years ago Closed 17 years ago

enter key does not work after opening two windows

Categories

(Firefox :: Address Bar, defect)

Product:
Firefox
Component:
Address Bar
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: kuahyeow, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9) Gecko/2008052912 Firefox/3.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9) Gecko/2008052912 Firefox/3.0 Opening two Firefox windows at the same time kills the enter key. (as of Firefox 3.0 RC2) People open two Firefox windows all the time, thinking the first click did not work. I would do that, and then close the extra window. Closing the extra window causes enter to not work on the remaining window. Reproducible: Always Steps to Reproduce: 1. Close all firefox instances. Open two firefox windows at the same. 2. On the second window, enter an address (e.g. www.yahoo.com) and press enter key. All should be normal 3. Close the second window. 4. On the first window, enter an address (e.g. www.yahoo.com) and press enter. Enter key does not work. Green 'go' button does not work Actual Results: nothing happens. no alerts, etc. Expected Results: the url is fetched upon pressing the enter key
Also happens in Firefox 2.0.0.14
I can't reproduce this. Are you launching it from the desktop shortcut, or clicking a link from another application, or what?
I am launching this from a shortcut on a Ubuntu Gnome Panel. The shortcut triggers the command 'firefox %u' One more thing to note is that this happens when you do not have saved tabs. I have recently upgraded to Firefox 3.0 and this still happens (see Steps to reproduce in description).
(In reply to comment #0) > Steps to Reproduce: > 1. Close all firefox instances. Open two firefox windows at the same. > 2. On the second window, enter an address (e.g. www.yahoo.com) and press enter > key. All should be normal > 3. Close the second window. > 4. On the first window, enter an address (e.g. www.yahoo.com) and press enter. > Enter key does not work. Green 'go' button does not work > Actual Results: > nothing happens. no alerts, etc. i can't reproduce this bug this way. but i have the same problem from time to time. i'm using firefox version 3.0.1 on WinXP 32bit. Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.1)
(In reply to comment #4) > i can't reproduce this bug this way. i can allways reproduce this bug, if i activate the add-on "Session Manager 0.6.1.13". <http://sessionmanager.mozdev.org/>
I'm the author of Session Manager and since someone filed a bug against Session Manager saying it caused this bug, I'm responding here. I cannot reproduce this bug with (or without) Session Manager installed. I don't run Linux, but a number of Session Manager users do and no one has ever reported this problem. For the record Session Manager does not listen for the enter key nor does it use or make any modifications to the location bar. Session Manager does listen for window close events, but it just uses that event to trigger grabbing the Window session data from the SessionStore API. If the enter key stops working only in the Ubuntu Linux version of Firefox that would appear to point to an issue with the Ubuntu version of Firefox.
I am the original poster of this bug. I do not have Session Manager installed that add-on does not cause this bug for me. However, If I disable all add-ons, then this bug disappears. Testing confirms that when Delicious Bookmarks 2.0.72 is the only add-on activated, the bug is reproducible.
not a bug in firefox - bug in delicious bookmarks
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Seems to be a duplicate of bug 376084.
That bug has no reproducible steps, and is a mess of add-on blame. anyway, this problem is not in firefox, but in delicious bookmarks 2.0.95 (still unsolved)
If this isn't in Firefox, then this bug shouldn't be filed either. I'd encourage you to consider that another add-on or even Firefox could be causing the problem for you, as most people discussing the issue on the Delicious extension mailing list have reported it fixed in the extension since, I think, 2.0.91.
Please read the ticket description and resolution. I would appreciate that a lot, or even better, help solve the problem, instead of complicating it with false dups and diversions.
You need to log in before you can comment on or make changes to this bug.