Revision 9b9293f0a667ca23ded04060894c2ce9e4a3e19c authored by Brian Birtles on 15 February 2018, 11:42:52 UTC, committed by moz-wptsync-bot on 15 February 2018, 11:42:52 UTC
These tests test the behavior introduced in the following changesets to the Web Animations specification: 1. https://github.com/w3c/csswg-drafts/commit/5af5e276badf4df0271bcfa0b8e7837fff24133a 2. https://github.com/w3c/csswg-drafts/commit/673f6fc1269829743c707c53dcb04092f958de35 which can be viewed as a merged diff at: https://gist.github.com/birtles/d147eb2e0e2d4d37fadf217abd709411 See the following spec issues: 1. https://github.com/w3c/csswg-drafts/issues/2059 2. https://github.com/w3c/csswg-drafts/issues/2266 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1436659 gecko-commit: 7465cb110ae5ec2e2ca73182caf5293f0efc8fd5 gecko-integration-branch: central gecko-reviewers: hiro
1 parent eb7491d
stub-4.5.4-opaque-response.html
<!DOCTYPE html>
<html>
<title>Service Workers: OpaqueResponse</title>
<head>
<link rel="help" href="https://w3c.github.io/ServiceWorker/#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>
Computing file changes ...