Closed Bug 1089912 Opened 6 years ago Closed 6 years ago
Create dom/security and move CSP and Mixed
Content Blocker into it
Since Bug 946065 already moved code from content/ into dom/ I think it's time to actually create dom/security and move CSP and also MixedContentBlocker into it. Ideally we would end up having: > dom/security/csp > dom/security/mixedcontentblocker and hopefully soon > dom/security/sri Additional note: I already filed Bug 1086619, so that we have not only CSP mochitests in one directory, but also mixed content tests.
Assignee: nobody → mozilla
Status: NEW → ASSIGNED
I think it's the better solution to move all the csp-files into > dom/security No need for additonal subfolders within security/. Once we land this patch we should also update: > https://wiki.mozilla.org/Modules/All#Content_Security
Comment on attachment 8512866 [details] [diff] [review] bug_1089912_1_move_csp_into_dom_security.patch Review of attachment 8512866 [details] [diff] [review]: ----------------------------------------------------------------- I think this looks good, but defer to jst.
Attachment #8512866 - Flags: review?(sstamm) → review+
When pushing to try  I realized that I forgot to add dom_security to all the different package-manifest files. incorporated that change now. Carrying over r+ from jst and sstamm.  https://tbpl.mozilla.org/?tree=Try&rev=56915b0016cf
Had to rebase this one as well after pulling mc. Carrying over r+ from jst and tanvi.
Here we go, try is green: > https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=2008ae73a2f4 Problem fixed by adding dom_security to the different pagacke-manigest files (see Comment 5). I will land soon, right after landing some csp changes, otherwise I would have to rebase those patches.
Target Milestone: --- → mozilla36
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.