554085 - Tab unexpectedly becomes new window on click in content border

Status: UNCONFIRMED

(Firefox :: Tabbed Browser, defect)

Description

[Rick]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.3pre) Gecko/20100321 Namoroka/3.6.3pre (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.3pre) Gecko/20100321 Namoroka/3.6.3pre (.NET CLR 3.5.30729)

Open firefox with multiple tabs one of which is to the URL http://online.wsj.com/home-page?refresh=on. The wsj tab should not be selected long enough for its page to be refreshed. After wsj page refreshed, select the wsj tab then click in the dark border area around the page's content. On click the tab becomes a new window. 

Reproducible: Always

Steps to Reproduce:
1.Open firefox with multiple tabs one of which is to the URL http://online.wsj.com/home-page?refresh=on.
2. Select a non-wsj tab.
3.Wait for the wsj tab to refresh its page.
4.After wsj tab refreshes its page, select the wsj tab.
5.Mouse click in the dark border surrounding the wsj page contents.
6. On click the tab becomes a new window.
Actual Results:  
Wsj tab unexpectedly becomes a new window.

Expected Results:  
Wsj tab remains a tab.

Put the tab in the new window back where it belongs in its previous window. The new window then closes.

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a4pre) Gecko/20100321 Minefield/3.7a4pre

I tested this but was not able to reproduce. Are you sure you didn't drag the tab to the dark border? Because then this behavior is expected.

Comment 2

[Rick]

I didn't drag the tab. However, further testing shows that the more tabs and windows open, the more reproducible it is. When testing, I make sure that the button-up event SHOULD have been queued (my clicking finger is off of the mouse) before I move the mouse into the wsj tab's content. That said, given that increasing tabs and windows (possibly concurrent refreshes of pages or some buffer overflow) has an effect on this bug, it will be harder to debug then it appeared when I filed the report. I will continue to sporadically attempt a
more definitive test case. In the mean time, it might be prudent to downgrade the bug to a more tolerable level.