Closed Bug 453576 Opened 16 years ago Closed 16 years ago

External link creates new tab on wrong browser window.

Categories

(Firefox :: Tabbed Browser, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 439054

People

(Reporter: lane, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1

I do not believe I had this problem prior to updating to 3.0.1.

This problem is occurring on sites that have an HTML splash page that when clicked on opens a new full-screen window for a flash page.  Once on the full-screen flash window, links to external sites should open a new tab in the full-screen window, bringing the contents of the link on top.  

Since the update, when clicking on the external link, the link is opened as a new tab on the old, splash page window behind the full-screen flash page window.  As a result, the user does not see that the link was activated.

For an example, please visit the following url:
http://www.icreations2.com/lane/#

Click the "ENTER SITE" link - a new fullscreen window should appear.

On the new window, select "blog" on the menu.  

On most browsers, a new tab is created in the fullscreen window.  When using Firefox, the new tab is created behind on the splash page.  

The bug only happens when someone has two windows open and they have open in new tab checked.

Reproducible: Always

Steps to Reproduce:
1.Firefox options: New Pages should be opened in: A new tab
2.visit http://www.icreations2.com/lane/#
3.click "ENTER SITE" link
4.open the menu on the flash site, click "blog"

Actual Results:  
The link opens on a new tab in the first window, behind the window currently being viewed

Expected Results:  
The link should open a new tab in the current window.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.