Open Bug 562478 Opened 14 years ago Updated 2 years ago

Consolidate default nsIContentPolicy implementations

Categories

(Core :: Networking, defect, P5)

Product:
Core
Component:
Networking
Type:
defect

Tracking

()

People

(Reporter: bsterne, Unassigned)

Details

(Whiteboard: [necko-would-take]) 

There are 5 implementations currently which all get called serially whenever Content Policy is checked:
http://mxr.mozilla.org/mozilla-central/search?string=::shouldload(

We should consolidate these into one or two implementations.
I'll take this.  Any thoughts on which implementations should be collapsed?
Assignee: nobody → bsterne
data document + nodataprotocol + cspservice are obvious options (since they all live in the same place, even).

nsWebBrowserContentPolicy I'm not sure about; does it depend on any other embedding/ bits?   Is nsContentBlocker actively used?
Whiteboard: [necko-would-take]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
Assignee: brandon → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.