File: inside-service-worker.https.html

package info (click to toggle)
firefox-esr 140.5.0esr-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 4,538,920 kB
  • sloc: cpp: 7,381,527; javascript: 6,388,905; ansic: 3,710,087; python: 1,393,776; xml: 628,165; asm: 426,916; java: 184,004; sh: 65,744; makefile: 19,302; objc: 13,059; perl: 12,912; yacc: 4,583; cs: 3,846; pascal: 3,352; lex: 1,720; ruby: 1,226; exp: 762; php: 436; lisp: 258; awk: 247; sql: 66; sed: 54; csh: 10
file content (27 lines) | stat: -rw-r--r-- 921 bytes parent folder | download | duplicates (22) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
 
<!DOCTYPE html>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>

<!--
  Set a policy in the document to ensure that the block is triggering
  in the worker and not in the document.
-->
<meta http-equiv="content-security-policy" content="connect-src 'self'">

<script>
  navigator.serviceWorker.register("./support/inside-worker.sub.js", { scope: "./support/" })
    .then(r => {
      var sw = r.active || r.installing || r.waiting;
      add_completion_callback(_ => r.unregister());

      // Forward 'securitypolicyviolation' events from the document into the
      // worker (we shouldn't actually see any, so the worker will assert that
      // none are fired.
      document.addEventListener('securitypolicyviolation', _ => {
        sw.postMessage("SecurityPolicyViolation from Document");
      });

      fetch_tests_from_worker(sw);
    });
</script>