Open Bug 1656582 Opened 5 years ago Updated 5 years ago

Restrict which JSMs can be loaded in content processes

Categories

(Core :: XPConnect, task, P3)

Product:
Core
Component:
XPConnect
Type:
task

Tracking

()

People

(Reporter: mccr8, Unassigned)

References

(Blocks 1 open bug)

Details

It might be nice to have an explicit allow list for JSMs that can be loaded in content processes. We have some tests for this at startup, but I'd imagine that there are lots of them that we never want to load in content processes. I'm not sure where this list would live. As usual with these sorts of things, an initial landing would just be some giant list that includes whatever and we would pare it down over time.

P3

Severity: -- → N/A
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.