Load about:mozilla and about:robots pages in a content process
Categories
(Core :: DOM: Content Processes, enhancement, P5)
Tracking
()
People
(Reporter: hazard-waltzer02, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
This bug is not caused by a user action.
Actual results:
about:mozilla and about:robots run in the chrome process.
Expected results:
These pages should be loaded in a content process instead, as they don't require any chrome privileges.
|
||
Comment 1•5 years ago
|
||
Resetting severity to default of --.
|
||
Comment 2•5 years ago
|
||
Hi,
Please let me know if you are referring to the about:performance screen within firefox, or the task manager within chrome
I will move this over to a component so developers can take a look over it. If is not the correct component please feel free to change it to an appropriate one.
Thanks for the report.
Best regards, Clara.
|
Reporter | |
Comment 3•5 years ago
|
||
(In reply to Clara Guerrero from comment #2)
Hi,
Please let me know if you are referring to the about:performance screen within firefox, or the task manager within chrome
I will move this over to a component so developers can take a look over it. If is not the correct component please feel free to change it to an appropriate one.
Thanks for the report.
Best regards, Clara.
about:mozilla and about:robots, not about:performance, it should still load as chrome.
|
||
Comment 4•5 years ago
|
||
WONTFIX. about:mozilla and about:robots can't easily be moved to a content process because they're specifically used by many tests for non-remote page loads. Plus, they're static web pages so there's not much security benefit from moving them out of the parent process.
|
|
Reporter | |
Comment 5•5 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #4)
WONTFIX. about:mozilla and about:robots can't easily be moved to a content process because they're specifically used by many tests for non-remote page loads. Plus, they're static web pages so there's not much security benefit from moving them out of the parent process.
Both about:mozilla and about:robots? Moving one of the two is acceptable and will fix the bug.
|
||
Comment 6•5 years ago
|
||
Yeah, also, a bug that is worth fixing, just maybe not worth the time investment in doing so right now, should probably never be marked as WONTFIX.
|
||
Updated•3 years ago
|
Description
•