Skip to main content

Browse the archive

https://github.com/web-platform-tests/wpt
26 December 2018, 22:31:15 UTC
Revision 9f72b689165309d4b959f3dbc724f18fe9a77111 authored by Mike West on 05 April 2018, 12:29:12 UTC, committed by Chromium WPT Sync on 05 April 2018, 12:29:12 UTC 
Add a runtime flag to restrict AppCache to secure contexts.
 
This patch adjusts the `SecureContext` IDL attribute to take an argument,
as we need to restrict the relevant bits and pieces to secure contexts
iff a specific flag is set. We'll unfortunately need to keep that in place
until and unless we decide that we can reasonably remove an enterprise
opt-out.

Intent to Deprecate/Remove: https://groups.google.com/a/chromium.org/d/msg/blink-dev/ANnafFBhReY/1Xdr53KxBAAJ
Spec bug: https://github.com/whatwg/html/issues/3440

Bug: 588931
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I5bedd2ca6f420a88ddbcff65e4223fad224ac0a7
Reviewed-on: https://chromium-review.googlesource.com/982625
Reviewed-by: Yoav Weiss <yoav@yoav.ws>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548391}
1 parent d725f2a
Raw File
Tip revision: 9f72b689165309d4b959f3dbc724f18fe9a77111 authored by Mike West on 05 April 2018, 12:29:12 UTC
Add a runtime flag to restrict AppCache to secure contexts.
Tip revision: 9f72b68
stub-4.1.7-service-worker-global-scope-onmessage.html 
<!DOCTYPE html>
<html>
<title>Service Workers: onmessage</title>
    <head>
        <link rel="help" href="https://w3c.github.io/ServiceWorker/#service-worker-global-scope-onmessage">
        <script src="/resources/testharness.js"></script>
        <script src="/resources/testharnessreport.js"></script>

    </head>
    <body>

<!--

`self.onmessage` is the [event handler][1] that must be supported as attribute
by the `ServiceWorkerGlobalScope` object. `ServiceWorkerGlobalScope` objects
act as if they had an implicit `[MessagePort][2]` associated with them. This
port is part of a channel that is set up when the worker is created, but it is
not exposed. This object must never be garbage collected before the
`ServiceWorkerGlobalScope` object.

All messages received by that port must immediately be retargeted at the
`ServiceWorkerGlobalScope` object. That is, an event named `message` using the
`[MessageEvent][3]` interface is dispatched on ServiceWorkerGlobalScope object.
The `event.source` of these `[MessageEvent][3]`s are instances of `[Client][4]`.



[1]: http://goo.gl/rBfiz0
[2]: http://goo.gl/tHBrI6
[3]: http://goo.gl/S5e0b6
[4]: #client-interface

-->



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

    </body>
</html>
back to top