Move CanAccess logic from DocShell to BrowsingContext
Categories
(Core :: DOM: Navigation, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: kmag, Assigned: kmag)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
BrowsingContext::CanAccess currently defers to nsDocShell to determine whether one BrowsingContext can navigate another. This means that it only works for in-process DocShells, and crashes when used with OOP contexts.
The existing DocShell logic is also much more complicated than it needs to be, given the current architecture. It was written in a time before named targetting was restricted to a single TabGroup/BrowsingContextGroup, which makes most of its remaining OriginAttributes and private browsing checks completely unnecessary.
![]() |
Assignee | |
Comment 1•6 years ago
|
||
This change is necessary in order to support named targeting of remote
BrowsingContexts, since the current arrangement only supports in-process
contexts. It also considerably simplifies the logic, since named targetting is
now restricted to the same TabGroup/BrowsingContextGroup, which in and of
itself guarantees that origin attributes will always match in the cases that
we care about.
![]() |
Assignee | |
Comment 2•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
![]() |
Assignee | |
Comment 3•6 years ago
|
||
![]() |
||
Comment 4•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/7bfc8b1c626d
https://hg.mozilla.org/mozilla-central/rev/783c0e44c713
![]() |
Assignee | |
Comment 5•6 years ago
|
||
![]() |
||
Comment 7•6 years ago
|
||
bugherder |
Description
•