Closed
Bug 422238
Opened 16 years ago
Closed 14 years ago
Confirmation windows get closed immediately after appearing
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: t, Unassigned)
Details
(Whiteboard: [CLOSEME 2010-07-30])
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008031104 Minefield/3.0b5pre Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008031104 Minefield/3.0b5pre Every new confirmation window is immediately closed. The typical windows ore 'Do you really want to quit?' or 'Do you really want to install this add-on?' The window disappears just before guessing a title bar for a milli second and focus returns to firefox main window. The nightly build is affected. I am running a debian unstable with fvwm2 as a window manager. Reproducible: Always Steps to Reproduce: 1. start firefox (duh ...) 2. get several tabs 3. try to close 4. a quick flicker indicates a possible confirmation window but ... no 5. return to firefox ... which hasn't been closed Actual Results: Firefox is not closed, but that's an example, installing an addon fails similarly Expected Results: firefox should ask you to confirm the closure or installation I noticed this quite a while ago on beta2 but thought it was due to my profile or my WM. I just retested it on beta1 and had the same buggy behaviour
Comment 1•14 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.x or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2010-07-30]
Version: unspecified → 3.0 Branch
Comment 2•14 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•