Consider severing the opener relationship on explicit navigations

NEW
Unassigned

Status

()

P3
normal
2 years ago
2 years ago

People

(Reporter: Nika, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
When the user types a URL into the addressbar, navigating to a new URL, that currently occurs within the toplevel browsing context of the current tab. This means that any other pages which have a reference to that browsing context, and the opener of that browsing context, remain linked to the new page. 

We should consider the webcompat implications and potential benefits which we could gain by making every explicit navigation through the URL bar create a distinct browsing context with a connected history.

Updated

2 years ago
Priority: -- → P3
Assignee: nobody → jkt
See Also: → bug 1341982
Assignee: jkt → nobody
One issue that should be considered is:

1. User is on example.com and it opens paypal.com
2. User switches back to example.com tab and changes the awesomebar to google.com
3. User then presses back on google window getting them to example.com

window.opener should probably be reconnected when the user is back on example.com.

One way to solve this might be to store the opener in the history and reconnect when the user is back on that page.
You need to log in before you can comment on or make changes to this bug.