Skip to main content

Browse the archive

Revision dac45e99114a10fae7dbc8105076aaef582f2bdc authored by Takayoshi Kochi on 26 April 2016, 12:42:20 UTC, committed by Hayato Ito on 26 April 2016, 12:42:20 UTC 
Document attributes should not leak shadow nodes (#2900)
 
Document attributes that returns HTMLCollection (document.all,
document.forms, etc.) should not leak any elements in shadow tree.

In this test, these attributes are tested:
 - document.scripts
 - document.all
 - document.forms
 - document.images
 - document.links
 - document.anchors
 - document.embeds
 - document.plugins
 - document.applets
1 parent db4eb13
Raw File
stub-4.5.4-opaque-response.html 
<!DOCTYPE html>
<html>
<title>Service Workers: OpaqueResponse</title>
    <head>
        <link rel="help" href="https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#opaque-response">
        <script src="/resources/testharness.js"></script>
        <script src="/resources/testharnessreport.js"></script>

    </head>
    <body>

<!--

`OpaqueResponse` objects are immutable but constructable. The `fetch()` API
returns this type for cross-origin responses.

Their role is to encapsulate the security properties of the web platform. As
such, their `body` attribute will always be `undefined` and the list of
readable `headers` is heavily filtered.

`OpaqueResponse` objects may be forwarded on to rendering documents in exactly
the same way as mutable `Response` objects.

-->



    <script>
        test(function() {
            // not_implemented();
        }, "There are no tests for section OpaqueResponse so far.");
    </script>

    </body>
</html>
back to top