Revision 260166c7aa434d6367910af87f67fdaf51146068 authored by Lukasz Anforowicz on 02 April 2018, 20:04:17 UTC, committed by Chromium WPT Sync on 02 April 2018, 20:04:17 UTC
Bug: 809261
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Idafb2b4cc5da3d6c7a054e479745288cc3b86513
Reviewed-on: https://chromium-review.googlesource.com/984338
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Nick Carter <nick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547494}
1 parent af485dc
postMessage_ports_readonly_array.htm
<!DOCTYPE html>
<title> postMessage(): read-only ports array </title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<div id=log></div>
<script>
"use strict";
async_test(function(t) {
var channel = new MessageChannel();
var targetPort = channel.port2;
targetPort.start();
targetPort.addEventListener("message", t.step_func_done(function(e) {
var channel3 = new MessageChannel();
assert_throws(new TypeError(), () => {
e.ports.push(channel3.port1);
}, "ports is a frozen object");
assert_equals(e.ports.length, 1, "ports is a read only array with length == 1.");
}), true);
var channel2 = new MessageChannel();
channel.port1.postMessage("ports", [channel2.port1]);
});
</script>
Computing file changes ...
