cc: Remove the --enable-partial-swap flag.

This flag only affects the cc::GLRenderer which is only
used when ubercomp is disabled. This means non-aura platforms.

On these platforms, the --enable-partial-swap flag is
never set, so we can turn it off permanently for non-ubercomp
renderer compositors. This removes the whole "AllowPartialSwap"
concept from content/renderer/ along with the command line
flag.


R=piman
BUG=

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

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252362 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252362
Made fling gestures always bubble between inner and outer viewports.

BUG=331958

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

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

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.

COLLABORATOR=rogerta@chromium.org
BUG=338127
R=jam@chromium.org, xiyuan@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252364 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252364
Create an interface WindowEventTarget to enable a class to receive
Windows input events.

This interface is defined in the newly added ui\base\window_event_target.cc/.h files.

It is implemented by the HWNDMessageHandler class. The class sets the interface as
window property on the HWND. The LegacyRenderWidgetHostHWND class retrieves this interface
via the window property and invokes the corresponding methods.

This is much cleaner than the current method of forwarding input messages from the
LegacyRenderWidgetHostHWND class via SendMessage and also avoids mucking with the
WPARAM of WM_MOUSEMOVE messages to ensure that the parent does not track those messages.

BUG=342323
R=sky@chromium.org
TBR=cpu

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252365 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252365
Add bool variables to name the enable_pixel_output param in tests.

These two tests don't give the boolean literal a name. They should.
The Vsync test used to claim to want pixel output but the test
passes without it, so leave pixel output disabled. For the ozone
software output device tests, only set enable_pixel_output true for
the test that compares the pixel output, though this flag is
meaningless for software compositing right now.

BUG=270918
R=dnicoara@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252366 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252366
Unify frame IDs with RenderFrameHost routing IDs.

This eliminates a lot of unnecessary code around FrameTreeNode::frame_id_, which was also incorrect if two frames had the same frame ID in different processes.

BUG=314791

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252370 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252370
AppendQuadsToFillScreen should compute quads in screen space.

This function may be adversely affected by root layer transforms.

R=danakj@chromium.org
BUG=344295

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252371 0039d316-1c4b-4281-b951-d872f2087c98
Removing rst files from Pepper API reference

This is so that the index.html files can load (instead of index.rst).

Chrome doc server doesn't support rst files.

NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252372 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252372
Use syzyasan instead of asan in chrome.gypi

R=siggi@chromium.org
TBR=chrisha@chromium.org, siggi@chromium.org

BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252373 0039d316-1c4b-4281-b951-d872f2087c98
Revert 252238 "NaCl SDK: Remove unsupported dev headers."

This change breaks the SDK builders (which are not yet in the CQ). Some of the
headers that were removed are required.

> NaCl SDK: Remove unsupported dev headers.
> 
> We shouldn't provide NaCl SDK headers for interfaces which are not available in
> NaCl. This change removes PPB_ interfaces that are not built on OS_NACL in
> ppapi/thunk/interfaces_ppb_public_dev.h
> 
> BUG=280338
> R=binji@chromium.org
> 
> Review URL: https://codereview.chromium.org/171703003

TBR=teravest@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252374 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 252374
RootWindowHostX11: Don't filter jittery mouse moves

A filter was put in place to filter jittery mouse moves a while
back. It worked by disallowing 1 pixel of reversed motion. The purpose
was to make rearranging apps in the app launcher feel smoother,
because those mouse moves were particularly impacted by the
then-jitteryness of the Chromebook Pixel touchpad.

We've since made the Pixel's touchpad not be jittery. Since this
filter does impact legitimate mouse moves, we should remove it.

BUG=344021
R=oshima@chromium.org

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

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