Fixing top-navigation in DCC

Adding in full DCC content_providers.json

Also slightly improving redirects.

Note that this starts off with patch https://codereview.chromium.org/148663007/.

Just made sense to deliver the content from this patch with restored navigation.

NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252143 0039d316-1c4b-4281-b951-d872f2087c98
[cc] Modify TestNextActionBeginsMainFrameIfNeeded

In the second and third test of TestNextActionsBeginsMainFrameIfNeeded,
they test when commit is requested. But, both tests doesn't set commit is needed.
Also, third test should check whether next action is BEGIN_MAIN_FRAME or not.

R=brianderson@chromium.org
BUG=NONE
TEST=cc_unittests --gtest_filter=*.TestNextActionBeginsMainFrameIfNeeded

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252144 0039d316-1c4b-4281-b951-d872f2087c98
Forward WM_NCHITTEST messages from the LegacyRenderWidgetHostHWND class to the parent window.

This is needed because there are cases when the bounds of the LegacyRenderWidgetHostHWND window and its parent
are the same. This also necessiates adding handlers for WM_NCXXX messages and forwarding them to the parent.

BUG=344775
R=cpu@chromium.org, cpu
TBR=jam

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252145 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252143
base: Add const to a few PlatformThreadHandle methods

BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252146 0039d316-1c4b-4281-b951-d872f2087c98
Removes #ash-enable-sticky-edges flag

BUG=343570
TEST=None

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252147 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252147
Remove pp_ifdef from grd files in components/.

Generated using:
> cd src/components
> git grep -l pp_ifdef | xargs sed -i "s:pp_ifdef('\([^']\+\)'):\1:g"

BUG=343235
R=joi@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252149 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252149
Roll DEPS for html-office-public

TBR=ganetsky@chromium.org
BUG=303491

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

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252151 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252151
[sync] Fix sync tests for Android.

This fixes and re-enables all the host driven sync tests.

NOTRY=true
BUG=329757,309997,311091

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252154 0039d316-1c4b-4281-b951-d872f2087c98
Prevents crash when docking a detached panel while fullscreen window is active

BUG=344909
TEST=Manual - follow steps in the bug.

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252155 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252154
SVN changes up to revision 252155
Reland r251495: Re-enable prerender RemovingLink browser tests.

The tests have changed significantly since they were first disabled. Add a
WaitForStop or two for good measure, but leave them as-is for the most part.
They can be disabled again if they still flake. Merge their custom prerender
loader into the main one; it's mostly the same.

In addition, for better test coverage, add a new test which asserts on events
received when a <link rel=prerender> is added for an existing prerender after
that prerender has loaded. Significantly rework the prerender events logic
to allow the test framework to wait on an event being received in the loader.

Fix implementation of set_loader_query_and_fragment to not produce URLs with
two ?s.

Original Review URL: https://codereview.chromium.org/142013004

BUG=167340, 128841

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252156 0039d316-1c4b-4281-b951-d872f2087c98
Fixes hover over keys changing cursor icon.

BUG=344943

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252157 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252157
Revert 251503 "Implement inline signin with iframe"

> Implement inline signin with iframe
> 
> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
> This is a dup of https://codereview.chromium.org/130963006/ since I cannot
> upload to that issue.  The only change is to address Xiyuan's two comments
> in patchset 3 of that CL.
> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
> 
> Inline signin chrome://chrome-signin is currently implemented using webview embedded in webUI, which breaks a couple of features in webUI and has serious accessbility issues. Since webview will be reimplemented based on OOPIF in the near future, and all the issues we have today will no longer apply, thus it is not worth the effort to fix them as they are throw away work. Instead, as suggested by John and prototyped in https://codereview.chromium.org/141363006/, we decide to switch to iframe instead. A few issues worth to mention,
> 
> 1. The iframe shares the same renderer as the embedder webUI, and thus could be potentially exposed to dangerous webUI privileges. John suggested a fix by assigning a unique storage partition ID to the inline signin page. As a result the inline signin and its embedded web content should never share the same renderer with other webUI pages.
> 
> 2. webview provides a direct API to inject script and to monitor requests/responses, which is not (directly) available with iframe. The CL works around the issue using content script and background script, quite similar to what CrOS is doing for SAML flow today. Thus it is also the first step towards unifying SAML flows on CrOS and desktop.
> 
> 3. with webview approach, we used to have a unique temporary partition for each instance of inline signin, in order to make sure multiple instances do not interfere with each other. This is more difficult with the iframe approach, since the partition ID is hardcoded in a quite low layer. In this CL, all inline signin pages share the same persistent partition, which means we have to handle the case when user loads the sign in page with a dirty cookie jar, and thus the newly connected user may not be stored in the primary session. The CL solves the issue by reading 'session_index' from 'google-accounts-signin' header.
> 
> BUG=338127
> 
> Review URL: https://codereview.chromium.org/134263005

TBR=rogerta@chromium.org

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

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