> On Oct 18, 2017, at 3:30 PM, Mike West <mk...@chromium.org> wrote: > > We do have `worker-src` tests, FWIW: > https://github.com/w3c/web-platform-tests/tree/master/content-security-policy/worker-src/ > > <https://github.com/w3c/web-platform-tests/tree/master/content-security-policy/worker-src/>. > We'll likely need to adjust things based on the fallback mechanism y'all are > running with (and Chrome will need to drop the weird contortions we > implemented for back-compat), but I'd hope you would be able to use those > rather than writing mochitests.
Quick update on worker-src: - We are going to ship worker-src with the fallback to child-src, script-src, default-src within Firefox 58. - There are some web-platform-tests, as pointed out by Mike, which we are going to extend within [1] to account for the fallback. Thanks, Christoph [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1409706 > > -mike > > On Wed, Oct 18, 2017 at 11:51 AM, Christoph Kerschbaumer <ckers...@gmail.com > <mailto:ckers...@gmail.com>> wrote: > > > On Oct 18, 2017, at 11:41 AM, James Graham <ja...@hoppipolla.co.uk > > <mailto:ja...@hoppipolla.co.uk>> wrote: > > > > On 18/10/17 10:35, Christoph Kerschbaumer wrote: > >>> On Oct 18, 2017, at 11:25 AM, James Graham <ja...@hoppipolla.co.uk > >>> <mailto:ja...@hoppipolla.co.uk>> wrote: > >>> > >>> On 22/09/17 15:18, Christoph Kerschbaumer wrote: > >>>> Hey Everyone, > >>>> within CSP2 workers used to be governed by the child-src directive [0]. > >>>> CSP3 introduces the worker-src directive [1] wich governs Workers, > >>>> SharedWorkers as well as ServiceWorkers. Please note that the child-src > >>>> directive has been deprecated within CSP3 in favor of worker-src as well > >>>> as frame-src. > >>>> For backwards compatibility child-src will still be enforced for: > >>>> * workers (if worker-src is not explicitly specified) > >>>> * frames (if frame-src is not explicitly specified) > >>>> We plan to ship the CSP directive worker-src within Firefox 58. > >>> > >>> Do we have cross-browser (i.e. web-platform) tests for this feature? > >> Not yet. We just agreed with Chrome on the same fallback mechanism, see > >> [1]. > >> We are about to add mochitests for all the different fallback mechanisms > >> though. > > > > What's the reason for writing mochitests? It seems like this is something > > where we benefit from shared tests. > > Reason is simple, I have already written the mochitests for it. But I agree, > we should have web-platform tests for it. > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org <mailto:dev-platform@lists.mozilla.org> > https://lists.mozilla.org/listinfo/dev-platform > <https://lists.mozilla.org/listinfo/dev-platform> > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform