Set WebViewImpl's size in OOPIF processes.

Set WebViewImpl's size in OOPIF processes.

In an OOPIF process with a remote main frame, currently the size of
the WebViewImpl is not set, because it is not relevant when there is
no main frame to render. However, the VisualViewport size is required
so OOPIF resizes set it appropriately.

This has caused a problem during printing because it saves and then
restores the WebViewImpl size, which unfortunately also wipes out the
VisualViewport size. This CL sets the WebViewImpl size along with
the VisualViewport in order to keep them consistent.

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation
BUG=705867
Review-Url: https://codereview.chromium.org/2801143002
Cr-Commit-Position: refs/heads/master@{#462927}
Committed: https://chromium.googlesource.com/chromium/src/+/931d158f73d21b37bad43543239a7da2f587ff0e

[kenrb, 2017-04-06 20:04:35]

Description was changed from

==========
Set WebViewImpl's size in OOPIF processes.

In an OOPIF process with a remote main frame, currently the size of
the WebViewImpl is not set, because it is not relevant when there is
no main frame to render. However, the VisualViewport size is required
so OOPIF resizes set it appropriately.

This has caused a problem during printing because it saves and then
restores the WebViewImpl size, which unfortunately also wipes out the
VisualViewport size. This CL sets the WebViewImpl size along with
the VisualViewport in order to keep them consistent.

BUG=705867
==========

to

==========
Set WebViewImpl's size in OOPIF processes.

In an OOPIF process with a remote main frame, currently the size of
the WebViewImpl is not set, because it is not relevant when there is
no main frame to render. However, the VisualViewport size is required
so OOPIF resizes set it appropriately.

This has caused a problem during printing because it saves and then
restores the WebViewImpl size, which unfortunately also wipes out the
VisualViewport size. This CL sets the WebViewImpl size along with
the VisualViewport in order to keep them consistent.

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation
BUG=705867
==========

[kenrb, 2017-04-06 20:04:45]

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

[commit-bot: I haz the power, 2017-04-06 20:05:57]

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-06 21:42:59]

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

[commit-bot: I haz the power, 2017-04-06 21:43:01]

Dry run: This issue passed the CQ dry run.

[kenrb, 2017-04-07 16:36:27]

kenrb@chromium.org changed reviewers:
+ dcheng@chromium.org

[kenrb, 2017-04-07 16:36:27]

dcheng: WDYT?

I'm not sure this change warrants a test, since I don't see a good place to put
one. When we refactor main frame sizing into a PageMsg then browser tests for
that should cover this behavior.

[dcheng, 2017-04-07 17:38:38]

LGTM

[kenrb, 2017-04-07 18:04:55]

The CQ bit was checked by kenrb@chromium.org

[commit-bot: I haz the power, 2017-04-07 18:05:26]

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-07 18:18:04]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1491588295416600, "parent_rev":
"1cdf325a6009c38dce43ea6ac9c866fdd9ef0ffc", "commit_rev":
"931d158f73d21b37bad43543239a7da2f587ff0e"}

[commit-bot: I haz the power, 2017-04-07 18:18:53]

Description was changed from

==========
Set WebViewImpl's size in OOPIF processes.

In an OOPIF process with a remote main frame, currently the size of
the WebViewImpl is not set, because it is not relevant when there is
no main frame to render. However, the VisualViewport size is required
so OOPIF resizes set it appropriately.

This has caused a problem during printing because it saves and then
restores the WebViewImpl size, which unfortunately also wipes out the
VisualViewport size. This CL sets the WebViewImpl size along with
the VisualViewport in order to keep them consistent.

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation
BUG=705867
==========

to

==========
Set WebViewImpl's size in OOPIF processes.

In an OOPIF process with a remote main frame, currently the size of
the WebViewImpl is not set, because it is not relevant when there is
no main frame to render. However, the VisualViewport size is required
so OOPIF resizes set it appropriately.

This has caused a problem during printing because it saves and then
restores the WebViewImpl size, which unfortunately also wipes out the
VisualViewport size. This CL sets the WebViewImpl size along with
the VisualViewport in order to keep them consistent.

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation
BUG=705867

Review-Url: https://codereview.chromium.org/2801143002
Cr-Commit-Position: refs/heads/master@{#462927}
Committed:
https://chromium.googlesource.com/chromium/src/+/931d158f73d21b37bad43543239a...
==========

[commit-bot: I haz the power, 2017-04-07 18:18:54]

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