Closed
Bug 1275485
Opened 9 years ago
Closed 9 years ago
Regression: can't close container that have been separated from the main window (can't close fx either and need to kill process)
Categories
(Core :: DOM: Security, defect, P1)
Tracking
()
VERIFIED
FIXED
mozilla49
Tracking | Status | |
---|---|---|
firefox49 | --- | fixed |
People
(Reporter: kjozwiak, Assigned: jhao)
References
(Blocks 1 open bug)
Details
(Whiteboard: [OA][userContextId][domsecurity-active])
Attachments
(1 file, 3 obsolete files)
6.76 KB,
patch
|
jhao
:
review+
|
Details | Diff | Splinter Review |
It looks like bug # 1271792 caused a nasty regression. When you drag a container tab out of the main window into it's own window, you won't be able to close it via the UI. The only way I managed to close it was to kill the entire process. I've reproduced this on all three platforms:
* Win 10 x64 VM - Reproduced
* Ubuntu 14.04.4 x64 VM - Reproduced
* OSX 10.11.15 x64 - Reproduced
I think this should be a P1 as it breaks normal functionality which is important for a broader m-c release.
STR: (very easy to reproduce)
* launch the latest version of m-c
* go into about:config and change privacy.userContext.enabled;true
* open a new container via File -> New Container Tab -> Personal
* once the tab opens, drag it into it's own separate window
* Now try closing the container window via:
** the "X" at the top right/left corner of the window (depending on the OS)
** Hamburger Menu -> Quit Button
** the "X" next to the container tab
You'll notice that you can't close the window/tab using the above methods. The only way that I managed to close the window/tab was to kill the entire process.
Regression range:
16:22.18 INFO: Last good revision: fe1a7608cfd77794732ce6d1f9a2ee7cc33e213f
16:22.18 INFO: First bad revision: 4df69b84d9e5d0ab1324523c1346ed8f2dd1439e
16:22.18 INFO: Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=fe1a7608cfd77794732ce6d1f9a2ee7cc33e213f&tochange=4df69b84d9e5d0ab1324523c1346ed8f2dd1439e
Reporter | ||
Updated•9 years ago
|
Summary: Regression: can't close container that have been separated from the main window (need to kill process) → Regression: can't close container that have been separated from the main window (can't close fx either and need to kill process)
Reporter | ||
Comment 1•9 years ago
|
||
I've also attached a video to illustrate the issue:
* https://youtu.be/hy1pno8eGcs
Assignee | ||
Comment 2•9 years ago
|
||
Thanks, Kamil, for catching this regression. I'll investigate the reason.
Assignee: nobody → jhao
Status: NEW → ASSIGNED
Updated•9 years ago
|
Assignee | ||
Comment 3•9 years ago
|
||
If I load a normal web page in the tab before dragging it, I can still close it normally. The regression happens when the tab is in about:newtab. It also happens on about:config, so probably there's something wrong with chrome pages.
In fact [1] could have solve bug 1271792. We make [2] because we thought some of baku's previous changes can be reverted. I tried backing out [2], and the regression is gone.
[1] https://hg.mozilla.org/integration/mozilla-inbound/rev/7cba66ab3465
[2] https://hg.mozilla.org/integration/mozilla-inbound/rev/8532f8ec8acd
Assignee | ||
Comment 4•9 years ago
|
||
Not only dragging about:xxx pages breaks, dragging normal webpages in non-e10s mode also breaks, so I'm going to put baku's changes in nsFrameLoader back. Sorry for causing this regression.
baku, could you review this patch? It is exactly the same as the one you wrote in 1260766.
Attachment #8757230 -
Flags: review?(amarchesini)
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Assignee | ||
Updated•9 years ago
|
Attachment #8757233 -
Attachment is obsolete: true
Assignee | ||
Updated•9 years ago
|
Attachment #8757232 -
Attachment is obsolete: true
Updated•9 years ago
|
Attachment #8757230 -
Flags: review?(amarchesini) → review+
Assignee | ||
Comment 7•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Keywords: checkin-needed
Assignee | ||
Updated•9 years ago
|
Attachment #8757230 -
Attachment is obsolete: true
Keywords: checkin-needed
Comment 10•9 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
Comment 11•9 years ago
|
||
Jonathan, thanks for fixing this regression quickly!
Kamil, thank you for filing this bug.
Could you help to verify the fix? :)
Flags: needinfo?(kjozwiak)
Reporter | ||
Comment 12•9 years ago
|
||
Went through verification using the following build:
* https://archive.mozilla.org/pub/firefox/nightly/2016/06/2016-06-02-03-02-20-mozilla-central/
* fx49.0a1 buildID: 20160602030220, changeset: 34a8be4346a9
* Opened all the different containers via several different methods:
** closed the container tab via the "X" next to the tab
** closed the container window via the "X" at the top right hand side of the window
** closed the FX via the Hamburger Menu
** closed the container tab via "File --> Close Tab"
** closed the container window via "File --> Close Window"
* ensured that I can drag several about:xxx pages into their own separate windows and close them via:
** closed the tab via the "X" next to the tab
** closed the window via the "X" at the top right hand side of the window
** closed the FX via the Hamburger Menu
** closed the tab via "File --> Close Tab"
** closed the window via "File --> Close Window"
* ensured that I can drag several web pages into their own separate windows via non-e10s and closed them via:
** closed the tab via the "X" next to the tab
** closed the window via the "X" at the top right hand side of the window
** closed the FX via the Hamburger Menu
** closed the tab via "File --> Close Tab"
** closed the window via "File --> Close Window"
I also went through the above test cases using a m-c debug build to ensure that there wasn't any assertions or crashes. Build Used:
* fx49.0a1 buildID: 20160602112746 changeset: 92e0c73391e7 tip
Status: RESOLVED → VERIFIED
Flags: needinfo?(kjozwiak)
You need to log in
before you can comment on or make changes to this bug.
Description
•