Move Mixed Content and Security state to BrowsingContext
Categories
(Core :: DOM: Security, enhancement, P3)
Tracking
()
People
(Reporter: djvj, Assigned: annyG)
References
(Blocks 1 open bug)
Details
(Whiteboard: [rm-docshell-tree-item:sync-state][domsecurity-backlog1])
The following pieces of state currently stored in documents needs to be replicated onto the BrowsingContext for bug 1585069:
BlockAllMixedContentPreloads
BlockAllMixedContent
UpgradeInsecurePreloads
UpgradeInsecure
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Christoph, IIUC, this is a Content Security bug. Kannan found this problem as part of his nsIDocShellTreeItem removal analysis for Fission. I don't know how this bug affects Fission users.
Tracking for Fission Nightly (M6) because this bug doesn't need to block dogfooding.
Comment 2•5 years ago
|
||
Yeah, I'll mark it block the Meta DOM:Security Fission Bug and we will look into it.
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Auditing whether this use of nsIDocShellTreeItem breaks when Fission is enabled blocks Fission Nightly.
Comment 4•5 years ago
|
||
This has become a duplicate of Bug 1631405.
Comment 5•4 years ago
|
||
Clearing Fission Milestone for bugs resolved as duplicates. We don't need to track duplicates.
Description
•