Closed
Bug 1267538
Opened 8 years ago
Closed 8 years ago
Dragging tabs out of the tabbar breaks with containers
Categories
(Core :: DOM: Security, defect)
Core
DOM: Security
Tracking
()
RESOLVED
DUPLICATE
of bug 1260766
People
(Reporter: ehsan.akhgari, Assigned: baku)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active][OA][userContextId])
STR: 1. Open a shopping container, and load a web page inside it. 2. Drag the tab out of the browser window to create a new window from it. 3. The newly opened tab will have the correct container UI but no content gets loaded inside it. 4. Furthermore, the tab will actually not really be in the container that the UI suggests. Rather, it seems to be opened in the default container.
Updated•8 years ago
|
Whiteboard: [domsecurity-active]
Updated•8 years ago
|
Blocks: ContextualIdentity
Comment 1•8 years ago
|
||
Using mozregression, received the following range: 24:27.35 INFO: Last good revision: 18963f8a2c46048c8c45f330799af71b118e34c6 24:27.35 INFO: First bad revision: 0d7b5a4fbffa4df34440e19c04e5628060315576 24:27.35 INFO: Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=18963f8a2c46048c8c45f330799af71b118e34c6&tochange=0d7b5a4fbffa4df34440e19c04e5628060315576 24:28.41 INFO: Looks like the following bug has the changes which introduced the regression: https://bugzilla.mozilla.org/show_bug.cgi?id=1242644
Updated•8 years ago
|
Whiteboard: [domsecurity-active] → [domsecurity-active][OA][userContextId]
Comment 2•8 years ago
|
||
For what it's worth, this was a purposeful change made in bug 1242644 to prevent people footgunning themselves, with bug 1260766 filed as the followup to fix it. Of which this appears to be a duplicate..
Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•