Safe Browsing has typically been considered its own toolkit sub-module, and isn't a "content security policy" the same way CSP/MCB are. I don't really have any objection to grouping it with the others in a new module, though.
The "DOM" in your proposed Bugzilla component name seems misleading - this stuff doesn't seem particularly DOM-related. Are there other upcoming/proposed code areas/features that you would see as also fitting under this module? Gavin On Fri, Feb 7, 2014 at 11:10 AM, Garrett Robinson <[email protected]> wrote: > There are several "content security policies" that live in DOM > or toolkit, but the owners/peers of those modules are not the people who > do the majority of the work writing or editing code for these > components. I propose we create a new "Content Security" module to house > these related features. The features in question are: > > * Content Security Policy (CSP) > * Mixed Content Blocker > * Safe Browsing > > Name: "Content Security" > Description: Security-related content policies > Location: dom/security > Owners: Sid Stamm, Gian-Carlo Pascutto > Peers: Garrett Robinson, Tanvi Vayas, Dan Veditz > Bugzilla Component: Core::DOM: Security (needs to be created) > > Source dirs/files: > > * toolkit/components/url-classifier > * content/base/+ > ** test/csp > ** src/CSPUtils.jsm > ** src/contentSecurityPolicy.js > ** src/CSPService.cpp/h > ** public/nsIContentSecurityPolicy.idl > ** src/nsMixedContentBlocker.cpp/h > ** test/{test,file}_mixed_content_* > _______________________________________________ > governance mailing list > [email protected] > https://lists.mozilla.org/listinfo/governance _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
