Closed
Bug 1688722
Opened 4 years ago
Closed 4 years ago
Remove uses of BrowsingContext::LegacyCheckOnlyOwningProcessCanSet
Categories
(Core :: DOM: Content Processes, defect, P3)
Core
DOM: Content Processes
Tracking
()
RESOLVED
FIXED
Fission Milestone | M8 |
People
(Reporter: cpeterson, Assigned: kmag)
References
(Depends on 1 open bug)
Details
Nika says, IIUC, all uses of BrowsingContext::LegacyCheckOnlyOwningProcessCanSet
are buggy. Some checks should use WindowContext::CheckOnlyOwningProcessCanSet
. Some checks should just be removed.
BrowsingContext::CheckOnlyOwningProcessCanSet
was renamed to LegacyCheckOnlyOwningProcessCanSet
in bug 1688715.
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Updated•4 years ago
|
Fission Milestone: ? → M7
Reporter | ||
Updated•4 years ago
|
Severity: -- → N/A
Priority: -- → P3
Updated•4 years ago
|
Assignee: nobody → kmaglione+bmo
Status: NEW → ASSIGNED
Type: task → defect
Updated•4 years ago
|
Whiteboard: [3/8] ETA: today
Comment 1•4 years ago
|
||
The necessary fix in Bug 1697271 is sufficient for M7, and the rest will follow up in M8, including devtools work.
Fission Milestone: M7 → M8
Whiteboard: [3/8] ETA: today
Comment 2•4 years ago
|
||
Let's close this one in favour of bug 1690100 which tracks all of the remaining work.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•