Fix secureContexts layout tests

Fix secureContexts layout tests

As alexmos@ noticed in https://codereview.chromium.org/1723753002/, the
secureContexts layout tests aren't very robust. They expect each frame
to send exactly one message, but in fact the frames were sending
messages to all of window.top, window.opener, and window.parent.

This CL makes the frames only send messages to window.top; as far as I
can tell there's no reason to send to window.opener or window.parent as
well.

BUG=

Committed: https://crrev.com/c6688e12756110ff918cac35584ffca59e2023cb
Cr-Commit-Position: refs/heads/master@{#378577}

[estark, 2016-02-29 23:21:50]

estark@chromium.org changed reviewers:
+ alexmos@chromium.org, mkwst@chromium.org

[estark, 2016-02-29 23:21:51]

mkwst, alexmos, PTAL? This is a prequel to
https://codereview.chromium.org/1723753002/ before I start revising that CL.

[estark, 2016-02-29 23:27:10]

added unauthenticated.html failure to test expectations, since it now fails as
expected with --site-per-process

[Mike West, 2016-03-01 13:45:22]

LGTM.

[alexmos, 2016-03-01 21:09:58]

LGTM

[estark, 2016-03-01 21:10:31]

The CQ bit was checked by estark@chromium.org

[commit-bot: I haz the power, 2016-03-01 21:11:28]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1745333002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1745333002/20001

[commit-bot: I haz the power, 2016-03-01 22:17:09]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-03-01 22:18:32]

Description was changed from

==========
Fix secureContexts layout tests

As alexmos@ noticed in https://codereview.chromium.org/1723753002/, the
secureContexts layout tests aren't very robust. They expect each frame
to send exactly one message, but in fact the frames were sending
messages to all of window.top, window.opener, and window.parent.

This CL makes the frames only send messages to window.top; as far as I
can tell there's no reason to send to window.opener or window.parent as
well.

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

to

==========
Fix secureContexts layout tests

As alexmos@ noticed in https://codereview.chromium.org/1723753002/, the
secureContexts layout tests aren't very robust. They expect each frame
to send exactly one message, but in fact the frames were sending
messages to all of window.top, window.opener, and window.parent.

This CL makes the frames only send messages to window.top; as far as I
can tell there's no reason to send to window.opener or window.parent as
well.

BUG=

Committed: https://crrev.com/c6688e12756110ff918cac35584ffca59e2023cb
Cr-Commit-Position: refs/heads/master@{#378577}
==========

[commit-bot: I haz the power, 2016-03-01 22:18:33]

Patchset 2 (id:??) landed as
https://crrev.com/c6688e12756110ff918cac35584ffca59e2023cb
Cr-Commit-Position: refs/heads/master@{#378577}