Closed Bug 1163385 Opened 9 years ago Closed 9 years ago

Cannot drag tabs such as about:config or about:preferences to another e10s window

Categories

(Firefox :: Tabbed Browser, defect)

Product:
Firefox
Component:
Tabbed Browser
Version:
40 Branch
Platform:
x86_64
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1094328

People

(Reporter: jinglesassy, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150509081231

Steps to reproduce:

Open about:config or other local settings pages, Drag it into another window.


Actual results:

It creates a new tab in the other window, However it does not load anything and on the original window it remains working until you change to another tab and try to reopen it, At which point the tab is unable to be reopened.


Expected results:

The tab should be closed on the original window and reopened on the second window.
Component: Untriaged → Tabbed Browser
OS: Unspecified → Windows 8.1
Priority: -- → P1
Hardware: Unspecified → x86_64
Please don't touch the Importance (Priority) field.
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
―――――――
Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150510030207
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150509081231

Browser Console shows
Error: Can only swap docshells between browsers in the same process.
chrome://global/content/bindings/browser.xml:1076:0
Status: UNCONFIRMED → NEW
status-firefox40: --- → affected
tracking-e10s: --- → ?
Depends on: 1012784
Ever confirmed: true
OS: Windows 8.1 → All
Priority: P1 → --
Summary: Cannot drag pages such as about:config or about:preferences to another tab in e10s. → Cannot drag tabs such as about:config or about:preferences to another e10s window
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox40: affected → ---
tracking-e10s: ? → ---
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.