Closed
Bug 1196159
Opened 10 years ago
Closed 9 years ago
[e10s] Window.closed returns false after calling Window.close()
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla45
People
(Reporter: xidorn, Assigned: mrbkap)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
Attachments
(2 files)
312 bytes,
text/html
|
Details | |
2.35 KB,
patch
|
billm
:
review+
|
Details | Diff | Splinter Review |
Steps to reproduce:
1. open the testcase in the attachment;
2. click the button "Open Window and Close";
3. wait for 2 seconds
Expected result:
the popup window is closed, and a dialog shows "Is window closed? true"
Actual result:
the popup window is closed, but the dialog shows "Is window closed? false"
Reporter | ||
Comment 1•10 years ago
|
||
This blocks enabling Fullscreen API tests on e10s because the test fullscreen-api-race relies on this.
Blocks: 1191597
Updated•10 years ago
|
Blocks: e10s-tests
tracking-e10s:
--- → +
Reporter | ||
Comment 2•9 years ago
|
||
It seems we call preventDefault() in DOMWindowClose so that we do not have mIsClosed set immediately.
:billm, any thoughts about this bug?
Blocks: 924260
Flags: needinfo?(wmccloskey)
Reporter | ||
Updated•9 years ago
|
I guess this is actually a webcompat bug. Need to re-triage.
Flags: needinfo?(wmccloskey)
Updated•9 years ago
|
Assignee: nobody → mrbkap
Assignee | ||
Comment 4•9 years ago
|
||
I'll wait for bug 967873 to land, since this will likely be related to that bug.
Depends on: 967873
Assignee | ||
Comment 5•9 years ago
|
||
Assignee | ||
Comment 6•9 years ago
|
||
Using preventDefault is using a very big hammer to avoid trying to close the actual window in the content process (especially because we send a message to the parent to do the actual closing). I thought about adding an API to tell the window that "yes, you're going to close" but that seems like overkill.
Of note here, once we send the DOMWindowClose message manager message, I don't think that the window *can't* close after that, so setting mIsClosed to true should be fine (thanks to bug 967873).
Attachment #8691043 -
Flags: review?(wmccloskey)
Attachment #8691043 -
Flags: review?(wmccloskey) → review+
Comment 8•9 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox45:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
Comment 9•9 years ago
|
||
Comment 10•9 years ago
|
||
Comment 11•9 years ago
|
||
Comment 12•9 years ago
|
||
Comment 13•9 years ago
|
||
Comment 14•9 years ago
|
||
Comment 15•9 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•