[wasm] Ensure postMessage doesn't work cross process.

[wasm] Ensure postMessage doesn't work cross process.

Wasm module structured cloning should not work over process boundaries.

BUG=

Review-Url: https://codereview.chromium.org/2847063002
Cr-Commit-Position: refs/heads/master@{#468742}
Committed: https://chromium.googlesource.com/chromium/src/+/b6567be47346a26d9e431c64d02e9176ae6a6308

[Mircea Trofin, 2017-04-28 04:09:39]

Description was changed from

==========
[wasm] Test postMessage doesn't pass moduless cross process.


BUG=
==========

to

==========
[wasm] Ensure postMessage doesn't work cross process.

Wasm module structured cloning should not work over process boundaries.

BUG=
==========

[Mircea Trofin, 2017-04-28 04:09:39]

mtrofin@chromium.org changed reviewers:
+ bradnelson@chromium.org, domenic@chromium.org, jochen@chromium.org

[Mircea Trofin, 2017-04-28 04:10:49]

Note that the error behavior currently being under specification isn't
incorporated in this change. The change just makes sure nothing makes it over
the boundary. Will update once aforementioned specification is wrapped up.

[Mircea Trofin, 2017-04-28 04:12:04]

The CQ bit was checked by mtrofin@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-28 04:12:55]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-28 05:22:55]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-04-28 05:22:55]

Dry run: This issue passed the CQ dry run.

[domenic, 2017-04-28 18:49:54]

This seems reasonable, although eventually we're going to need a comprehensive
suite of tests similar to what's already in
https://github.com/w3c/web-platform-tests/tree/master/html/infrastructure/saf...
. (Those tests will be imported into
https://codesearch.chromium.org/chromium/src/third_party/WebKit/LayoutTests/e...
within a day or so.)

It may be good to try to copy the structure of those tests, and place them in
external/wpt/html/infrastructure/safe-passing-of-structured-data/wasm-module, so
that they are automatically upstreamed. But I can understand wanting to do just
a quick smoke test for Chrome-only for now.

[jochen (gone - plz use gerrit), 2017-05-02 09:15:12]

https://codereview.chromium.org/2847063002/diff/1/third_party/WebKit/LayoutTe...
File third_party/WebKit/LayoutTests/http/tests/wasm/resources/remote_frame.html
(right):

https://codereview.chromium.org/2847063002/diff/1/third_party/WebKit/LayoutTe...
third_party/WebKit/LayoutTests/http/tests/wasm/resources/remote_frame.html:5:
if(!ret) ret = "didn't make it"
nit. space after if

https://codereview.chromium.org/2847063002/diff/1/third_party/WebKit/LayoutTe...
File
third_party/WebKit/LayoutTests/http/tests/wasm/wasm_remote_postMessage_test.html
(right):

https://codereview.chromium.org/2847063002/diff/1/third_party/WebKit/LayoutTe...
third_party/WebKit/LayoutTests/http/tests/wasm/wasm_remote_postMessage_test.html:7:
if (window.location.origin != get_host_info().HTTPS_REMOTE_ORIGIN) {
just name the file wasm_remote_postMessge_test.https.html then it'll
automatically start on https

[Mircea Trofin, 2017-05-02 18:00:34]

The CQ bit was checked by mtrofin@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-02 18:00:57]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Mircea Trofin, 2017-05-02 19:08:00]

ptal

[jochen (gone - plz use gerrit), 2017-05-02 19:08:34]

lgtm

[commit-bot: I haz the power, 2017-05-02 19:18:25]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-02 19:18:26]

Dry run: This issue passed the CQ dry run.

[Mircea Trofin, 2017-05-02 19:22:27]

The CQ bit was checked by mtrofin@chromium.org

[commit-bot: I haz the power, 2017-05-02 19:22:53]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-02 19:29:46]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1493752947683800,
"parent_rev": "f15458b47ffa2d9a13db0ca70a2ea3d3e27bcd3e", "commit_rev":
"42b8079dbcc830066897529ace7919f32d5b5938"}

[commit-bot: I haz the power, 2017-05-02 19:30:07]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1493752947683800,
"parent_rev": "d61caeda8451fe13bd74e403dd78faf96e620e17", "commit_rev":
"b6567be47346a26d9e431c64d02e9176ae6a6308"}

[commit-bot: I haz the power, 2017-05-02 19:30:53]

Description was changed from

==========
[wasm] Ensure postMessage doesn't work cross process.

Wasm module structured cloning should not work over process boundaries.

BUG=
==========

to

==========
[wasm] Ensure postMessage doesn't work cross process.

Wasm module structured cloning should not work over process boundaries.

BUG=

Review-Url: https://codereview.chromium.org/2847063002
Cr-Commit-Position: refs/heads/master@{#468742}
Committed:
https://chromium.googlesource.com/chromium/src/+/b6567be47346a26d9e431c64d02e...
==========

[commit-bot: I haz the power, 2017-05-02 19:30:54]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/b6567be47346a26d9e431c64d02e...