This function is called over JNI to determine wheter a particular
size of memory allocation will leave us in a low memory state.
Bug: 5142892
Change-Id: I3d0f85075497c2a374cd866b0223eecaaa4b5f46
Track pad taps will have a duration of 300ms, so we need to take this
into account when handling touch events in the WebView.
Bug: 5076008
Change-Id: Ia0d7ad88637b1f6b85440283ab29086a5f60fdba
bug:5062896
Depends on external/webkit change:
https://android-git.corp.google.com/g/#change,125566
Loads pages from SD card, and scrolls through them reporting results. Added
contentInvalidateAll hidden WebView method, and made pageSwapCallback
extensible.
Change-Id: I9f7377aad6fd7c101177dde552a72357c8b4e400
bug:5008210
Redraw the WebTextView when the page swaps (and thus the background is updated)
That way it updates at (approximately) the same time as the page. In software
rendering, do as before.
Depends on following external/webkit change:
https://android-git.corp.google.com/g/#change,124606
Change-Id: I59d7266a49d0ba734efdb88fef5fafe68aecfbce
bug:5008210
Still has the following issues:
* colors are always black & white
* ignores centering, word wrap from text area
* gray background text (such as with instant search) and other textfield effects
aren't shown
The DebugFlags.DRAW_WEBTEXTVIEW can still be used to overlay red text over the
input box.
Change-Id: I7f22321c31b9edbc5351cac13f2e17b0ee19d563
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
