Added keyset transition tests for the virtual keyboard. Specifically we test:
1) Transitions between all valid pairs of keysets.
2) Persistant capitalization between keyset changes.


BUG=295066

Review URL: https://codereview.chromium.org/25687007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@227646 0039d316-1c4b-4281-b951-d872f2087c98
Added method to Launcher.

Added method to ash Launcher returning rectangle bounding all visible elements
in launcher.

BUG=269286
TEST=ash_unittests --gtest_filter=*LauncherViewVisibleBoundsTest*

Review URL: https://codereview.chromium.org/26014003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@227647 0039d316-1c4b-4281-b951-d872f2087c98
The attestation-content-protection setting should be true by default.

BUG=chromium:302842
TEST=manual

Review URL: https://codereview.chromium.org/26026002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@227648 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 227648
Linux sandbox: Allow the GPU process to go past 4GB

The GPU process is currently limited to 4GB of address space,
which causes crashes in some legitimate cases (the canonical
example is to open a ton of empty tabs on Chrome OS, when the
GPU process's virtual address space reaches 4GB it crashes).

This didn't use to be a problem for Chrome OS before we had
compressed swap as we were limited to 4GB of physical memory,
but now that we have compressed swap and that a lot of Chrome OS
machines are switching to 64 bit, it is possible to get there
without problems.

To fix this, we bump the maximum size of the GPU process's
address space to 16GB on 64 bit.

BUG=chromium:271119
TEST=open a ton of tabs, see VIRT go beyond 4096M in top and the GPU process doesn't crash

Review URL: https://codereview.chromium.org/26102002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@227649 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 227649