File: child-src-about-blank-allowed-by-default.sub.html

package info (click to toggle)
firefox-esr 140.5.0esr-1~deb13u1
  • links: PTS, VCS
  • area: main
  • in suites: trixie-proposed-updates
  • size: 4,539,036 kB
  • sloc: cpp: 7,381,527; javascript: 6,388,905; ansic: 3,710,087; python: 1,393,776; xml: 628,165; asm: 426,918; 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 (29 lines) | stat: -rw-r--r-- 1,095 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
28
29
 
<!DOCTYPE html>
<html>

<head>
    <!-- Programmatically converted from a WebKit Reftest, please forgive resulting idiosyncracies.-->
    <meta http-equiv="Content-Security-Policy" content="child-src 'none'; object-src 'none'; script-src 'self' 'unsafe-inline'; connect-src 'self';">
    <title>child-src-about-blank-allowed-by-default</title>
    <script src="/resources/testharness.js"></script>
    <script src="/resources/testharnessreport.js"></script>
    <p>These frames should not be blocked by Content-Security-Policy.
        It&apos;s pointless to block about:blank iframes because
        blocking a frame just results in displaying about:blank anyway!
    </p>
    <script>
        var t = async_test("Check that frames load without throwing any violation events");
        window.addEventListener("securitypolicyviolation", t.unreached_func("Should not have fired any events"));
    </script>

    <iframe src="about:blank"></iframe>
    <object type="text/html" data="about:blank"></object>

    <div id="log"></div>

    <script>
        t.done();
    </script>
</body>

</html>