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)

Product:
Core
Component:
DOM: Navigation
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla71
Project Flags:
Fission Milestone M4
Tracking Flags:
Tracking Status
firefox71 --- fixed

People

(Reporter: smaug, Assigned: smaug)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Bug 1586793 - [Fission] iframe.contentWindow may be null when it shouldn't be, r=peterv
47 bytes, text/x-phabricator-request
Details | Review

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.

Assignee: nobody → bugs
Blocks: fission-mochitests
Fission Milestone: --- → M4
Priority: -- → P2

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

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

https://hg.mozilla.org/mozilla-central/rev/821fdad0dbb2

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.

Attachment

General

Creator:
Created:
Updated:
Size: