Closed
Bug 1586793
Opened 5 years ago
Closed 5 years ago
[Fission] iframe.contentWindow may be null when it shouldn't be
Categories
(Core :: DOM: Navigation, defect, P2)
Core
DOM: Navigation
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
bug 1580391 shows that .contentWindow can be null when it shouldn't be.
The iframe element there is in DOM all the time, but at some point
.contentWindow becomes null.
|
||
Updated•5 years ago
|
|
Assignee | |
Comment 1•5 years ago
|
||
The other cases when ClearWindowProxy is called seem to be fine.
It is the Unlink case which was causing null .contentWindow with test_mozfiledataurl.html
Fixes bug 1580391 and backs out bug 1581004
|
|
Assignee | |
Comment 2•5 years ago
|
||
Pushed by opettay@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/821fdad0dbb2 [Fission] iframe.contentWindow may be null when it shouldn't be, r=peterv
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox71:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
You need to log in
before you can comment on or make changes to this bug.
Description
•