Set the browser window bounds to fit to the Xvfb's size

Set the browser window bounds to fit to the Xvfb's size.

Chrome for ChromeOS currently places the window at 200x200 with 1366x768 size by default. This puts the parts of UI outside of Xvfb window, where the mouse cursor cannot be moved into.

Default size is 1280x1024 and I'm using the 1280x800 that is one of resolution actually used on the device.

BUG=None

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

[oshima, 2015-09-24 17:54:50]

oshima@chromium.org changed reviewers:
+ phajdan.jr@chromium.org

[oshima, 2015-09-24 17:58:03]

Patchset #1 (id:1) has been deleted

[oshima, 2015-09-24 17:58:38]

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

[commit-bot: I haz the power, 2015-09-24 17:59:32]

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

[commit-bot: I haz the power, 2015-09-24 18:44:59]

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

[commit-bot: I haz the power, 2015-09-24 18:45:00]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[oshima, 2015-09-24 19:53:27]

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

[commit-bot: I haz the power, 2015-09-24 19:56:51]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1360233005/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1360233005/40001

[commit-bot: I haz the power, 2015-09-24 20:43:16]

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

[commit-bot: I haz the power, 2015-09-24 20:43:16]

Dry run: This issue passed the CQ dry run.

[Paweł Hajdan Jr., 2015-09-25 10:46:50]

Is there a reason to put it here as opposed to
src/content/public/test/browser_test_base.cc ?

[oshima, 2015-09-26 01:31:53]

On 2015/09/25 10:46:50, Paweł Hajdan Jr. wrote:
> Is there a reason to put it here as opposed to
> src/content/public/test/browser_test_base.cc ?

content can't depend on ash. This makes sense for tests that use ash, so it's
less useful
for tests under content/ and extensions/.

[Paweł Hajdan Jr., 2015-09-28 09:44:13]

LGTM

[oshima, 2015-09-28 15:41:05]

The CQ bit was checked by oshima@chromium.org

[commit-bot: I haz the power, 2015-09-28 15:41:47]

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

[commit-bot: I haz the power, 2015-09-28 16:14:01]

Committed patchset #2 (id:40001)

[commit-bot: I haz the power, 2015-09-28 16:15:19]

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