Closed
Bug 1603007
Opened 5 years ago
Closed 5 years ago
Remove browser.tabs.remote.allowLinkedWebInFileUriProcess
Categories
(Core :: DOM: Content Processes, task, P3)
Core
DOM: Content Processes
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox77 | --- | fixed |
People
(Reporter: pbone, Assigned: pbone)
References
Details
Attachments
(1 file)
Remove browser.tabs.remote.allowLinkedWebInFileUriProcess after fission and document channel ship and are always used.
|
||
Comment 1•5 years ago
|
||
Fix after Fission MVP ships
Fission Milestone: ? → Future
Summary: [fission] Remove browser.tabs.remote.allowLinkedWebInFileUriProcess → Remove browser.tabs.remote.allowLinkedWebInFileUriProcess after Fission ships
|
Assignee | |
Updated•5 years ago
|
Assignee: nobody → pbone
Status: NEW → ASSIGNED
See Also: → 1626583
Summary: Remove browser.tabs.remote.allowLinkedWebInFileUriProcess after Fission ships → Remove browser.tabs.remote.allowLinkedWebInFileUriProcess
|
|
Assignee | |
Comment 2•5 years ago
|
||
This patch removes the allowLinkedWebInFileUriProcess pref, but one
code-path is kept because when DocumentChannel is disabled a HTTP POST load
from a file:// page would loose the postData, so that case keeps the FILE
remote type.
Pushed by pbone@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b25250e2c618
Remove allowLinkedWebInFileUriProcess r=nika
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox77:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla77
You need to log in
before you can comment on or make changes to this bug.
Description
•