Open
Bug 1362331
Opened 8 years ago
Updated 2 years ago
When a file:// URI browsing context is the only top level in its tab group, it should process switch on navigation to http.
Categories
(Core :: DOM: Content Processes, enhancement, P3)
Core
DOM: Content Processes
Tracking
()
NEW
People
(Reporter: bobowen, Unassigned)
References
(Depends on 1 open bug)
Details
(Whiteboard: sb+)
When a top level browsing context that has a file:// URI page loaded is navigated to a URI that would not normally be loaded in the file content process and it is the only top level in its tab group, then it should be safe (non-web observable) to process switch to a normal content process.
We want to do this as the normal content process will have a more secure sandbox.
Currently POST data is lost from history entries on process switch, so there is at least some observable behaviour change.
Updated•7 years ago
|
Priority: -- → P3
Whiteboard: sb+
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•