Disable console output from the test, to ignore msg diff for x-site frames.

Disable console output from the test, to ignore msg diff for x-site frames.

Without OOPIFs the console message emitted during the test looks as
follows:

  CONSOLE ERROR: line 8: Unsafe JavaScript attempt to initiate navigation
  for frame with URL
  'http://127.0.0.1:8000/security/frameNavigation/sandbox-DENIED-top-navigation-without-user-gesture.html'

With OOPIFs only the origin is known:

  CONSOLE ERROR: line 8: Unsafe JavaScript attempt to initiate navigation
  for frame with origin 'http://127.0.0.1:8000' ...

This CL makes sure the test output is the same with and without OOPIFs,
by disabling logging of console output.  The validation of the main
thing the test wants to test (whether top-level navigation happened
or not) is still happening by verifying if the child frame stayed
at its current location (which wouldn't have happened if its top-level
parent was navigated) - this is verified by checking if the child frame
still contains the following text:

  The top navigation from this iframe should be blocked.
  This text should appear.

BUG=682726
TEST=Run the layout test with and without --site-per-process

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

[Łukasz Anforowicz, 2017-01-19 17:52:50]

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

[commit-bot: I haz the power, 2017-01-19 17:53:20]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Łukasz Anforowicz, 2017-01-19 17:53:53]

lukasza@chromium.org changed reviewers:
+ japhet@chromium.org

[Łukasz Anforowicz, 2017-01-19 17:53:54]

Nate, could you PTAL?  This CL should make site isolation bots green again.  See
the bug and the CL description for explanation why it is 1) necessary and 2)
okay to disable console output.

[Nate Chapin, 2017-01-19 18:46:20]

lgtm

[commit-bot: I haz the power, 2017-01-19 18:51:17]

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

[commit-bot: I haz the power, 2017-01-19 18:51:17]

Dry run: This issue passed the CQ dry run.

[Łukasz Anforowicz, 2017-01-19 18:59:01]

The CQ bit was checked by lukasza@chromium.org

[commit-bot: I haz the power, 2017-01-19 18:59:50]

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-01-19 19:05:43]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1484852341931520, "parent_rev":
"f2c4a3b373c281d37f2a92717ebb63f7787463ba", "commit_rev":
"ea3bb6bbd7ff85c64dd603505ba7822dd86cff16"}

[commit-bot: I haz the power, 2017-01-19 19:06:15]

Description was changed from

==========
Disable console output from the test, to ignore msg diff for x-site frames.

Without OOPIFs the console message emitted during the test looks as
follows:

  CONSOLE ERROR: line 8: Unsafe JavaScript attempt to initiate navigation
  for frame with URL
 
'http://127.0.0.1:8000/security/frameNavigation/sandbox-DENIED-top-navigation-without-user-gesture.html'

With OOPIFs only the origin is known:

  CONSOLE ERROR: line 8: Unsafe JavaScript attempt to initiate navigation
  for frame with origin 'http://127.0.0.1:8000' ...

This CL makes sure the test output is the same with and without OOPIFs,
by disabling logging of console output.  The validation of the main
thing the test wants to test (whether top-level navigation happened
or not) is still happening by verifying if the child frame stayed
at its current location (which wouldn't have happened if its top-level
parent was navigated) - this is verified by checking if the child frame
still contains the following text:

  The top navigation from this iframe should be blocked.
  This text should appear.

BUG=682726
TEST=Run the layout test with and without --site-per-process
==========

to

==========
Disable console output from the test, to ignore msg diff for x-site frames.

Without OOPIFs the console message emitted during the test looks as
follows:

  CONSOLE ERROR: line 8: Unsafe JavaScript attempt to initiate navigation
  for frame with URL
 
'http://127.0.0.1:8000/security/frameNavigation/sandbox-DENIED-top-navigation-without-user-gesture.html'

With OOPIFs only the origin is known:

  CONSOLE ERROR: line 8: Unsafe JavaScript attempt to initiate navigation
  for frame with origin 'http://127.0.0.1:8000' ...

This CL makes sure the test output is the same with and without OOPIFs,
by disabling logging of console output.  The validation of the main
thing the test wants to test (whether top-level navigation happened
or not) is still happening by verifying if the child frame stayed
at its current location (which wouldn't have happened if its top-level
parent was navigated) - this is verified by checking if the child frame
still contains the following text:

  The top navigation from this iframe should be blocked.
  This text should appear.

BUG=682726
TEST=Run the layout test with and without --site-per-process

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

[commit-bot: I haz the power, 2017-01-19 19:06:17]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/ea3bb6bbd7ff85c64dd603505ba7...