Closed
Bug 1646513
Opened 5 years ago
Closed 5 years ago
Fix GetInProcessParentDocument usage in CheckForSubFrameDrop
Categories
(Core :: DOM: Copy & Paste and Drag & Drop, defect)
Core
DOM: Copy & Paste and Drag & Drop
Tracking
()
RESOLVED
FIXED
mozilla80
Tracking | Status | |
---|---|---|
firefox80 | --- | fixed |
People
(Reporter: kmag, Assigned: kmag)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
We only allow drops from descendant frames into ancestors if they're same origin anyway, which implies same-process, but outside of Fission, we allow cross-origin interstitial frames, whereas with Fission we currently don't due to the way we walk the ancestor tree.
Assignee | ||
Comment 1•5 years ago
|
||
We only allow drops from descendant frames into ancestors if they're same
origin anyway, which implies same-process, but outside of Fission, we allow
cross-origin interstitial frames, whereas with Fission we currently don't due
to our walking the ancestor tree using GetInProcessParentDocument.
Pushed by maglione.k@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/f17be2edac14
Fix GetInProcessParentDocument usage in CheckForSubFrameDrop. r=nika
Comment 3•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox80:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in
before you can comment on or make changes to this bug.
Description
•