Load chrome: URLs through parent process

NEW
Unassigned

Status

()

defect
P3
normal
4 years ago
2 years ago

People

(Reporter: billm, Unassigned)

Tracking

(Blocks 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: sb+)

Filing this based on bug 1136407. If we prevent the content process from accessing the profile directory, then we need to give it a way to access chrome: URLs. Otherwise, add-ons won't be able to load frame scripts.

Jed, please dupe this if it's already filed. I couldn't find anything.

Updated

4 years ago
Blocks: 1083344

Comment 1

4 years ago
This bug is also affecting at least Mac but I don't know for Windows, so I refrain from changing platform to "all". Bugzilla offers not multiple choice option here.

Updated

4 years ago
Blocks: 1124817
I filed bug 1109293 for something similar with resource: URLs.  In that bug I suggested that they resolve to the remoteopenfile: scheme instead of file:, to reuse the code that currently makes app:// work on B2G, but there might be a better way than that.

Updated

3 years ago
Whiteboard: sbwc2

Updated

3 years ago
Whiteboard: sbwc2 → sbwc3

Updated

2 years ago
Blocks: 922481
Priority: -- → P3
Whiteboard: sbwc3 → sb+
You need to log in before you can comment on or make changes to this bug.