Updating trunk VERSION from 1654.0 to 1655.0

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225831 0039d316-1c4b-4281-b951-d872f2087c98
Automated Commit: Committing new LKGM version 4747.0.0 for chromeos.

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225839 0039d316-1c4b-4281-b951-d872f2087c98
[InfoBar] Upstream the translate infobar implementation and one of its tests

BUG=158817

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225840 0039d316-1c4b-4281-b951-d872f2087c98
Do not clear validation errors on focus/edit

This CL adds the notion of whether a section has been submitted without
changing the suggestion item or data source. If a user has attemped to
submit an invalid section without changing either of these, validation
errors should "stick" until the user edits each input.

This CL also adds a concept of "sureness" to the validation messages
passed back from the controller. Because the controller does not have
all the contextual information it needs, just keep this info in the
view and pass back data on whether it's sure the input is invalid (or
unsure, in which case it's the view's responsibility to handle
validation based on context).

This is a continuation of dbeam's work on https://codereview.chromium.org/23618011/

BUG=235239

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225841 0039d316-1c4b-4281-b951-d872f2087c98
First cut at sharing server config between youtube servers.

R=rch@chromium.org, jar@chromium.org

NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225842 0039d316-1c4b-4281-b951-d872f2087c98
[rAC, OSX] Use new layout for the details section.

Adjusted layout to reflect latest mocks.

NOTRY=true
BUG=286518

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225843 0039d316-1c4b-4281-b951-d872f2087c98
Update V8 to version 3.22.3.2.

TBR=danno@chromium.org
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225844 0039d316-1c4b-4281-b951-d872f2087c98
Update .DEPS.git

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225845 0039d316-1c4b-4281-b951-d872f2087c98
[rAC] Added clarifying comment.

BUG=299877
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225846 0039d316-1c4b-4281-b951-d872f2087c98
Make the SigninGlobalError multi-login aware.

BUG=277149
R=asvitkine@chromium.org, atwilson@chromium.org, courage@chromium.org, fgorski@chromium.org
TBR=asvitkine@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225847 0039d316-1c4b-4281-b951-d872f2087c98
Revert 225847 "Make the SigninGlobalError multi-login aware."

> Make the SigninGlobalError multi-login aware.
> 
> BUG=277149
> R=asvitkine@chromium.org, atwilson@chromium.org, courage@chromium.org, fgorski@chromium.org
> TBR=asvitkine@chromium.org
> 
> Review URL: https://codereview.chromium.org/23875028

TBR=rogerta@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225848 0039d316-1c4b-4281-b951-d872f2087c98
Pepper API implementation for output protection.

BUG=256538
R=cpu@chromium.org, dalecurtis@chromium.org, dmichael@chromium.org, marcheu@chromium.org, wuchengli@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225849 0039d316-1c4b-4281-b951-d872f2087c98
Relanding this as the previous attempt failed on linux aura

Perform the window activation code in WM_ACTIVATE instead of WM_NCACTIVATE.

This ensures that we don't inadvarently mark a window as active when the code uses APIs like FlashWindow,
which send periodic WM_NCACTIVATE messages to flash the caption.

BUG=297813
TEST=Covered by ui test WidgetNotActivatedOnFakeActivationMessages
TBR=sky@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225851 0039d316-1c4b-4281-b951-d872f2087c98
Update Quickoffice (Beta) to 31.91.1417

This CL updates the component extension manifest files with the
correct version number.

BUG=294882
NOTRY=true
TESTING=manual

Change-Id: I72e7e5b1b640363772008eb9bb773583d7bc9141

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225855 0039d316-1c4b-4281-b951-d872f2087c98
Cleanup of QuicInMemoryCache to sync with internal version.

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=225588

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225856 0039d316-1c4b-4281-b951-d872f2087c98
gfx: Create a separate gfx component out of ui.

BUG=103304
R=ben@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225857 0039d316-1c4b-4281-b951-d872f2087c98
Allow clipping by scroll parents.

Previously, we had required that we inherit our clip from our direct ancestor or
our clip parent (which has to be an ancestor). This CL loosens that restriction
and allows clipping by our scroll parent, which will not be our ancestor.

In order for this to work, we must ensure that the scroll parent's clip is
computed before we compute the clip children's. This is accomplished by changing
the order in which we recur through the layer tree and sorting layer lists
afterward to ensure that we ultimately stack correctly.

NB: I have taken care to only sort the newly added layers, and to only sort when
the child order has actually changed, which should happen rarely.

Tests:
 1. LayerTreeHostCommonTest.ClippedByScrollParent
   - Checks that the simple case (where the scroll parent is naturally processed
     before the scroll child) results in the correct clips.
 2. LayerTreeHostCommonTest.ClippedByOutOfOrderScrollParent
   - Identical to (1) but checks that clips are still correct when the scroll
     parent needs to be visited out of order.
 3. LayerTreeHostCommonTest.ClippedByOutOfOrderScrollGrandparent
   - Similar to (2), but also checks that clips are set up correctly if the
     scroll parent has yet another scroll parent (sorting for recursion is a bit
     tougher in this case).
   - Also checks that despite visiting layers out of order, that the layer list
     ends up in paint order.
 4. LayerTreeHostCommonTest.OutOfOrderClippingRequiresRSLLSorting
   - Similar to (3), but includes several render surfaces in the tree and checks
     that the resulting render surface layer list is ordered correctly.
5. LayerTreeHostCommonTest.DoNotClobberSorting
   - Ensures that if we have to reorder layer list contributions that we do not break 3d sorting.

BUG=291413
R=danakj@chromium.org, enne@chromium.org, hartmanng@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225858 0039d316-1c4b-4281-b951-d872f2087c98
Revert 225857 "gfx: Create a separate gfx component out of ui."

> gfx: Create a separate gfx component out of ui.
> 
> BUG=103304
> R=ben@chromium.org
> 
> Review URL: https://codereview.chromium.org/25015003

TBR=sadrul@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225859 0039d316-1c4b-4281-b951-d872f2087c98
Revert 225858 "Allow clipping by scroll parents."

> Allow clipping by scroll parents.
> 
> Previously, we had required that we inherit our clip from our direct ancestor or
> our clip parent (which has to be an ancestor). This CL loosens that restriction
> and allows clipping by our scroll parent, which will not be our ancestor.
> 
> In order for this to work, we must ensure that the scroll parent's clip is
> computed before we compute the clip children's. This is accomplished by changing
> the order in which we recur through the layer tree and sorting layer lists
> afterward to ensure that we ultimately stack correctly.
> 
> NB: I have taken care to only sort the newly added layers, and to only sort when
> the child order has actually changed, which should happen rarely.
> 
> Tests:
>  1. LayerTreeHostCommonTest.ClippedByScrollParent
>    - Checks that the simple case (where the scroll parent is naturally processed
>      before the scroll child) results in the correct clips.
>  2. LayerTreeHostCommonTest.ClippedByOutOfOrderScrollParent
>    - Identical to (1) but checks that clips are still correct when the scroll
>      parent needs to be visited out of order.
>  3. LayerTreeHostCommonTest.ClippedByOutOfOrderScrollGrandparent
>    - Similar to (2), but also checks that clips are set up correctly if the
>      scroll parent has yet another scroll parent (sorting for recursion is a bit
>      tougher in this case).
>    - Also checks that despite visiting layers out of order, that the layer list
>      ends up in paint order.
>  4. LayerTreeHostCommonTest.OutOfOrderClippingRequiresRSLLSorting
>    - Similar to (3), but includes several render surfaces in the tree and checks
>      that the resulting render surface layer list is ordered correctly.
> 5. LayerTreeHostCommonTest.DoNotClobberSorting
>    - Ensures that if we have to reorder layer list contributions that we do not break 3d sorting.
> 
> BUG=291413
> R=danakj@chromium.org, enne@chromium.org, hartmanng@chromium.org
> 
> Review URL: https://codereview.chromium.org/23536049

TBR=vollick@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225860 0039d316-1c4b-4281-b951-d872f2087c98
Fix middle mouse drag cursor without regressing menu-over-link cursor

A previous change
https://src.chromium.org/viewvc/chrome?revision=224273&view=revision to fix
the mouse cursor not being set properly over menus caused a regression in
middle-mouse dragging. Because the root window doesn't get focus until after
the mouse down, the middle drag cursor doesn't get set on mouse down as it
should.

So, instead of using RootWindow focus, check that there's not another top
level window (like the menu) above the root window that's asking to set the
cursor instead.

R=ben@chromium.org
BUG=292379,299286

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225861 0039d316-1c4b-4281-b951-d872f2087c98