Closed
Bug 320579
Opened 19 years ago
Closed 19 years ago
If a message box pops up while moving or reordering tabs, the mouse clicks are unresponsive on Firefox
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 246801
People
(Reporter: poolfish666, Unassigned)
References
()
Details
(Keywords: hang)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
If a message box pops up while moving or reordering tabs, the mouse clicks are unresponsive on Firefox until you close the message box. You can still use the arrow keys and tab key on they keyboard to move the focus around the buttons on the message box and the enter key or spacebar to activate that button. Also pressing Atl+F4 doesn't do anything.
Reproducible: Always
Steps to Reproduce:
1. Open at least 2 tabs
2. In one tab goto any website (or don't go anywhere)
3. In the other tab goto https://mail.yahoo.com/ and immediately left mouse click and drag that tab like you're reordering it and hold down the left mouse button until the "Security Error: Domain Name Mismatch" message box comes up
Actual Results:
Any mouse clicks are unresponsive on Firefox until you close the message box by other means.
Expected Results:
The tab that was being reordered should go back to it's original place and the user should be able to click the buttons on the message box.
I've testing this with 3 different themes (Firfox default, Noia 2.0 eXtreme 2.992 and PimpZilla 3.08) and on 2 different OS's (Windows 2000 and Windows 98 SE) with the same results.
Related to/duplicate of bug 246801 and/or bug 315125?
Comment 2•19 years ago
|
||
*** This bug has been marked as a duplicate of 246801 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Comment 3•17 years ago
|
||
V.Duplicate
Severity: minor → normal
Status: RESOLVED → VERIFIED
Keywords: hang
Version: unspecified → 1.5.0.x Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•