Don't expose an nsIChannel to document-on-opening-request
Categories
(Core :: DOM: Navigation, enhancement, P3)
Tracking
()
| Fission Milestone | Future |
People
(Reporter: mattwoodrow, Unassigned)
References
(Blocks 1 open bug)
Details
document-on-opening-request exposes the DocumentChannelChild to observers as an nsIChannel*.
This is a bit unfortunate, as DocumentChannel only partially implements this interface, so new code/observers could easily be broken - https://searchfox.org/mozilla-central/rev/a37fc61f172b432e7ae0b6b4c4a12cac2a787a0f/netwerk/ipc/DocumentChannel.cpp#312
Bug 1617500 is also aiming to make the nsILoadInfo on DocumentChannelChild not available (or even less accurate than it currently is).
Ideally we'd have another interface for the subset of data that we can actually guarantee to be available in the content process, and pass this.
ExtensionPolicyService is currently using this observer notification, grabbing the nsILoadInfo, and accessing quite a few members.
|
||
Updated•6 years ago
|
|
||
Updated•5 years ago
|
|
||
Updated•4 years ago
|
Description
•