Autofill was reading the WebView's WebSettings on a background thread.
Move it to the UI thread to conform to the WebView API and get rid of a
Strict Mode violation.
Bug: 5072283
Change-Id: Ib0ac60697f1e629ac1ef1743545b5cf0ac2cf52a
bug:5062896
Added features to TileProfiler, updated jni interface to allow querying of
arbitrary log data via strings. Depends on the following webkit change:
https://android-git.corp.google.com/g/#change,122779
For new logging jni interface, and logging of invalidates.
Change-Id: I80ba6702b87e86ec76e5b0eafde45f4ef3a80ad3
Bug: 5002925
White list certain messages that can be handled after WebViewCore
was destroyed (specificially pause/resumeTimers, which are per process)
and reject all other messages. This avoids using the undocumented
removeCallbacksAndMessages(null) trick, as well as makes sure PAUSE_TIMERS
and RESUME_TIMERS are processed in the correct order the correct number
of times.
Change-Id: I8c51172e015f923ffeb0816a8ee2ab63219d0f96
The Autofill server is now configured as a system setting. Add
that setting and a method to be called over JNI from the chrome
stack to retrieve it.
See also external/chromium change I3a22ae42402f52207eee2d0d9df64700cb7c9f45
Bug: 4515820
Change-Id: I0aa85c5bef834b1120baaabdc2dd2e4e607a63b6
It was done so we would have the name "ViewRoot" available for a
public API. However, the name "ViewAncestor" just makes no sense.
So instead, change it to ViewRootImpl.
Change-Id: If9599ca67896f339f6fefa7d1dde121201171d97
These strings had a defintion native side, but no corresponding
definition java side which would lead to a crash. Strings taken from
chrome/app/generated_resources.grd - see
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/generated_resources.grd?r1=75912&r2=76117&pathrev=88489
Also note that credit_card_number_preview_format is no longer needed.
See also change Ib861245e26197938bb2c5cf0f99c1d797ab0fbf2
Change-Id: I829b5d24e6f9a04211ee91c3f670c8659c004cd9
If mInitialScale is set, use it as the default scale; otherwise,
it'll be overridden by default density in case of book app where
mobile fixed viewport is used; since today the default scale is used
to calculate the mobile fixed viewport.
issue: 4982074
Change-Id: I21c2bf41478bb97351cb3fb1cc3735ab7d75e164
Update viewport as soon as possible to make sure layout has correct viewport.
This helps fixes gmail flickering issue.
Also helps the case a mobile site is switched to desktop when the
user agent is switched.
issue: 4723800
Change-Id: I3dc9e52d912d49478d562cec3f38d653a563715e
The Java object should remain usable until the WebView is navigated
away from the current page. The native side holds only a weak
reference, so we need to keep a reference Java-side.
Bug: 4990734
Change-Id: I40bd078f779228480cfe6f52d9feb4e60c963b4b
We must not call WebView.destroy() until after the WebView has been
removed from the view hierarchy.
Bug: 4974517
Change-Id: I33b3a9d4ec098e2ab50626cb8906da7697ff2a33
Once we switch out from full screen mode, the player will be re-created for the
next video, we should release the sources as early as possible.
bug:4332676
Change-Id: I4c26523b3600d3100f81e422979236fca57beb7c
In case of non-standard load such as reload, currently the ZoomManager's
onFirstLayout will not be triggered, hence initial zoom overview will not
be set.
This change provides a fix to set initial zoom overview in case of
non-standard load for the new picture after first layout.
issue: 4975315
Change-Id: If2ba3e472f2bb7b6fc4c52024d18a66dc1e41a23
