New session from tearoff retains focus of parent session




9 years ago
8 years ago


(Reporter: tgarrison, Unassigned)


3.5 Branch
Windows XP

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2011-2-25])



9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)

When tearing a tab off to a new window, the focus of the parent window is handled by the new child window in what appears to be a dialog manner.

Reproducible: Always

Steps to Reproduce:
1. Open multiple tabs in a browser session
2. Drag one of the tabs to a new window (tearoff)
3. Attempt to click anywhere in the parent browser window
Actual Results:  
The parent browser receives no events and the child browser window "flashes", as if focus is being lost and immediately regained.

Expected Results:  
The parent and child browser instances should function seemingly independently.

This behavior was noticed primarily with jQuery-enabled pages, but was able to be replicated with any page style.
Does this also happen in safe-mode / with a new profile?
Version: unspecified → 3.5 Branch

Comment 2

9 years ago
The bug was able to be replicated in both safe mode and a new fresh profile. I have also noticed that this seems to occur only when the parent browser window is maximized.
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a1pre) Gecko/20090928 Minefield/3.7a1pre

You probaby mean that you drag a tab onto the taskbar and release it there. Then I can reproduce the problem. This problem seems fixed on trunk. Can you retest?

Comment 4

9 years ago
It does seem to be fixed in trunk, though I will have to wait until Monday to confirm.

I was not dragging the tab to the taskbar; it was being dragged to an empty space on my screen. I don't know if it's worth mentioning that this happened with a multiple monitor setup, but that should be relatively apparent by the behavior I have no explained.

I will update this report on Monday with my findings.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is
far gone. If the reporter can still see this issue, Please retest with Firefox
3.6.x or later and a new profile
( Then please remove the
closeme tag in the whiteboard, mark the bug against the proper version and
comment on the bug.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.