Issue 4866 - Add the child-src CSP directive back again for now

lib/csp.js

 /*
  * This file is part of Adblock Plus <https://adblockplus.org/>,
  * Copyright (C) 2006-2016 Eyeo GmbH
  *
  * Adblock Plus is free software: you can redistribute it and/or modify
  * it under the terms of the GNU General Public License version 3 as
  * published by the Free Software Foundation.
  *
  * Adblock Plus is distributed in the hope that it will be useful,
  * but WITHOUT ANY WARRANTY; without even the implied warranty of
@@ skipping 16 matching lines @@
   let match = defaultMatcher.matchesAny("", RegExpFilter.typeMap.WEBSOCKET,
                                         hostname, false, null, true);
   if (match instanceof BlockingFilter)
   {
     details.responseHeaders.push({
       name: "Content-Security-Policy",
       // We're blocking WebSockets here by adding a connect-src restriction
       // since the Chrome extension API does not allow us to intercept them.
       // https://bugs.chromium.org/p/chromium/issues/detail?id=129353
       //
-      // We also need the child-src and object-src restrictions since CSPs are
+      // We also need the frame-src and object-src restrictions since CSPs are
       // not inherited from the parent for documents with data: and blob: URLs.
       // https://bugs.chromium.org/p/chromium/issues/detail?id=513860
       //
-      // We must use the deprecated child-src directive instead of the
-      // combination of frame-src and worker-src directives since worker-src
-      // is not yet supported (as of Chrome 56.)
+      // We must use the deprecated child-src directive instead of worker-src
+      // since that's not supported yet (as of Chrome 56.)
       //
       // "http:" also includes "https:" implictly.
       // https://www.chromestatus.com/feature/6653486812889088
-      value: "connect-src http:; child-src http:; object-src http:"

[Wladimir Palant, 2017/03/01 13:17:58]

1.12.4 was using both frame-src and child-src. For the sake of not introducing
regressions shortly before a release, I suggest that you add child-src in
addition to frame-src instead of replacing it.

[kzar, 2017/03/01 14:41:18]

Done.

+      value: "connect-src http:; child-src http:; frame-src http:; object-src http:"
     });
     return {responseHeaders: details.responseHeaders};
   }
 }, {
   urls: ["http://*/*", "https://*/*"],
   // We must also intercept script requests since otherwise Web Workers can
   // be abused to execute scripts for which our Content Security Policy
   // won't be injected.
   // https://github.com/gorhill/uBO-Extra/issues/19
   types: ["main_frame", "sub_frame", "script"]
 }, ["blocking", "responseHeaders"]);