GitLab

Cherry-pick of Chromium crrev.com/r227614

BUG: 9103603

PictureImageLayerImpl ignores PictureLayerImpl::ideal_content_scale_ and
conditionally sets tile scale to 1.f. This makes the comparison in
PictureLayerImpl::AppendQuads to check for incomplete tiles incorrect.

Fix by overriding PictureImageLayerImpl::CalculateContentsScale to
always set ideal_content_scale_ to 1.f.

Fix for internal bug b/9103603.

TEST=PictureImageLayerImplTest.IgnoreIdealContentScale

Change-Id: Ib73dedd91e60d16a8610b4e6b8e560bfa4e12966

Cherry-pick of Chromium crrev.com/227508

Bug: 11065663

Original description:

The AwQuotaManagerBridge needs to be usable from any thread, not just
the UI thread. Make it refcounted and have its methods post to the UI
thread if not already there. Since none of the methods are synchronous
there's no need to wait for the posted messages to be handled.

BUG=305205
R=benm@chromium.org

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

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

This commit was generated by merge_to_master.py.

Change-Id: I0ee9cadd8d40aa5fea7450dadb93244110642752

This commit was generated by merge_to_master.py.

Change-Id: Icbada855096943f29f59aa9bfe136f26dd055024

Cherry-pick of Chromium crrev.com/r227261

BUG: 11086057

Original description:

If shrinksStandaloneImagesToFit is true, then it breaks single image
documents in wrap contents mode.

Change-Id: Ie52f6eba207d210f3fbc8a80d7d449272f5047e0

BUG: 11001058

Webview does not use ProactiveBeginFrame, so cannot depend on BeginFrame
for activation.

Note that this patch as is cannot land in upstream Chromium since all
other platforms do use ProactiveBeginFrame.

Forking since Chromium trunk looks very different so fixes there cannot
be cherry-picked now.

Change-Id: I6a6e2e6f9dcfc7b29d0af2e0f04e2e042610380e

Cherry pick of https://codereview.chromium.org/25453008/

Bug: 7882891

Original Description:
[Android WebView] Disable WebRTC.

Android WebView compiles out WebRTC, so we should disable runtime
interfaces too.

Change-Id: I72da32a95af8feb395a144a64a267061a6179fd0

Cherry pick of https://chromiumcodereview.appspot.com/25878003/

Bug: 10825362

Original Description:
[Android WebView] Add an API to control favicon loading.

Change-Id: If752842bbff8f5b07719d84d69cad8bb4642bd45

Refactor the CookieManager to allow it to be used without starting
Chromium. If Chromium has not been started when the cookie manager is
first used, a temporary cookie monster will be created and used to
service requests (with its own client/backend threads). If the app
subsequently triggers regular Chromium startup (e.g. by creating a
WebView) then the temporary one will be shut down cleanly before the
real instance is created.

Bug: 10969703
Change-Id: I903630cbdbccc61958e5e8b9179c0a3d09594a8b

Cherry-pick of Chromium crrev.com/r226947

BUG: 11063091

Original description:

The instance of AwContentsIoThreadClient is uninstalled when AwContents
(along with WebContents and RenderViewHost) is destroyed. But RenderView
can still be alive and send more requests. It may also be possible for
AwContentsIoThreadClient to be uninstalled after a request has started.
So null check all usage of AwContentsIoThreadClient::FromID to make sure
it returns a real object.

Change-Id: I17e7b7a8cccb6e833a8a176a236437688891dd16

Merge "Cherry-pick: [Android] Prevent re-entrance into ContentVideoView.exitFullscreen" into klp-dev

Cherry-pick of Chromium crrev.com/r226859

BUG: 11057493

Original description:

For Android WebView, if app decides to call exitFullscreen from
onDestroyContentVideoView, then re-entering into exitFullscreen and
causing an infinite recursion.

Fix by moving the onDestroyContentVideoView to after removeSurfaceView.
The next time destroyContentVideoView in, onDestroyContentVideoView will
not be called since mVideoSurfaceView is already null.

Change-Id: I5c4de70d1fe34a82e3393ed7d9164555040f5919

Cherry-pick of Chromium crrev.com/r226844

BUG: 11048885

Original description:

This is to reduce the number of gpu memory buffer allocations which
can consume multiple file descriptors.

Change-Id: Ifa525d26a02dc4ba6af0821d8f4f911c2ab71c17

Bug 10932261

This allows the AwSettings (java only) instance to be created in advance
of AwContents, thereby allowing the AwSettings to be used early on when
the chromium stack has not be fully started.
As a result AwSettings is now able to live as a 'dumb' Java container of
settings, prior to the chromium stack being initialized at all.

Change-Id: I4059a93a7ad132043998fe2eab318a3b066c882e

Bug 10932261

Originally from http://crrev.com/25092005/ PS9, but modified to land
in klp-dev.

Original Description:
[Android] Android code should not assume main thread == UI thread.

Although typically the case, the main thread of an android app is not
necessarily the thread in which the View is hosted (the Android "UI"
thread). Update base.ThreadUtils to be able to specify a non-main thread
UI thread, and update places in the code that make this assumption to
use the refactored ThreadUtils class.

Change-Id: Ie2967fedafcece90f4e65b52a84bdd21f6b745cd

Cherry-pick of Chromium crrev.com/r226676

BUG: 10951963

Original description:

We can never assume that calling View invalidate will lead to a draw,
since view can be invisible, off screen, clearView, etc so draw will
be optimized out. Therefore must always ensure that the fallback tick
matches what the compositor expects, ie if compositor expects a
BeginFrame, then we must always have a pending tick.

One case where this does not hold true is if a DrawGL clip does not
cover the entire visible area, we call invalidate, set block_invalides
to true, but does not schedule a fallback tick. Until the next draw
comes, webview remains in a live lock situation that no more fallback or
invalidates will be called.

Fix by not setting block_invalidates in this case so subsequent fallback
ticks can still be scheduled.

Change-Id: I469ea26094e5e8f0c00f4c94663d776d59b6d266

Cherry-pick of Chromium crrev.com/r226643

Conflicts:
	android_webview/browser/in_process_view_renderer.cc

BUG: 10606165

Original Description:

In OnMemoryPressure, drop tiles on invisible browser views.

Not reusing base::MemoryPressureListener because Android
WebView requires onTrimMemory to be called synchronously.

Change-Id: I5aaca024392ef964baac0bc53f554ea59b8dac41

Cherry-pick of Chromium crrev.com/r226104

BUG: 10932261

Original description:

In Android, a short lived EGL context is created on the UI thread during
start up to collect GPU info. One side effect is that if there is an
existing EGL context current, then it is released. This is a problem for
Android WebView but may affect Chrome as well.

This patch saves and restores the existing current context if there is
one.

Change-Id: I4efec482833a6e06e81d22711935ac2b937756ce

Cherry-pick of Chromium crrev.com/226442

BUG: 10606165

Original description:

NICE_TO_HAVE will pre-render the soon-bin, which is based on both
velocity and distance. Previously, EVERYTHING will also pre-render the
eventually bin. NICE_TO_HAVE is a better fit for the Android WebView
memory management model where we assume a webview will not go berserk
with memory.

Note that this can still fill up on fling.

Change-Id: Iba36767172c89ac59d0209769940cf8c33f6571f

This commit was generated by merge_to_master.py.

Change-Id: I519469a0c5a5f59b10dc02dcc6c5621cb667b5ab

This commit was generated by merge_to_master.py.

Change-Id: Ia939b5ad3e3e3d32216275d1f1c4ea7407440e37

Cherry-pick of chromium crrev.com/25496002

BUG: 10959756

Original description:

When a full tree synchronization happens, the ScrollOffsetDelegate
is called too early (i.e. before DidBecomeActive()) and sees always
a 0x0 scroll offset.
This CL swaps the call order of SetRootLayerScrollOffsetDelegate
and DidBecomeActive during the active tree activation in
LayerTreeHostImpl::ActivatePendingTree.
Updating also the unit tests to prevent future regressions
on the RootLayerScrollOffsetDelegate.

BUG=b/10959756
TBR=mkosiba@chromium.org

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

Change-Id: Ib95bdb8403ae367490550dea0963a166cbc5a428

Cherry-pick of chromium crrev.com/25505005

Bug: 10911057

Original decription:
Early out if contentviewcore native side is null.

BUG=b/10911057

Early out before calling native getNavigatonHistory as it may be
deleted before.

Change-Id: I3efccaeafe2a1b56408742e907ba0e6afcfcabf5

Cherry-pick of Chromium crrev.com/r226254

This is a speculative fix for b/10951963.

BUG: 10951963

Original description:

Make sure all software composite (draws, capture picture,
fallback tick) will reschedule fallback tick.

Also make sure fallback tick is cancelled only after all
early out code.

Change-Id: I66625dc493e29f2a2687835ffb12a7d2a0d97eaa

Cherry-pick of Chromium crrev.com/225905

BUG: 10606165
Change-Id: I1c994fb1f9b5fc6a159ce823d8dc5db13c6b9eb5

Cherry-pick of Chromium crrev.com/r225736

BUG: 10606165

Original description:

For low end and low resolution devices, allocation steps of 10M is too
coarse, so lower it down to 5M. This also affects small WebViews.

Also lower the multiplier to 10 to be more conservative.

Change-Id: I91f90dcda59cc68210414a5454e5dcef96f06c19

Merge "Cherry pick [Android WebView] Populate WebKit WebPreferences correctly in browser" into klp-dev

Merge "Cherry pick [Android] When toggling AX script inject, also set native AX state." into klp-dev

Cherry pick of https://codereview.chromium.org/23619089/

Bug: 10911684

Orignal description:
Currently Android WebView will push settings from the java side to the
renderer, but if the browser needs to read those settings back we will
use a default set from WebContentsImpl as we neglect to override
ContentBrowserClient::OverrideWebKitPrefs. This means that the browser
and renderer can see out of sync preference values.

Change-Id: Id466e29c009cb1d91cdab8eac8997de14f014657

This commit was generated by merge_to_master.py.

Change-Id: If451c530d0c6b67850aa33f17a128f39e3680d0d

This commit was generated by merge_to_master.py.

Change-Id: I8dd637c3a839c16cbab4d0b6b1edbfc557986168

Cherry pick of https://codereview.chromium.org/24559002/

Bug: 10911684

Original description:
[Android] When toggling AX script inject, also set native AX state.
When we enable/disable script injection, also update the flag that
says whether we should use native accessibility.

Change-Id: I6ff2ee7cb0309ec0f279178245056a6de3df560c