Bug: 5321358
Destroy does run with this. Ideally we should get rid of the need
to run this on the UI thread at all. GL destroy should instead
take place when the view is detached or something like that.
Cherry picked from master
Change-Id: I693ce83cd607186173d8cf58485c5df28004e52c
nativeSetIsScrolling has other side effects. Just pause picture
updating when WebView loses focus.
Change-Id: I917851c806f35a91a12a25c7457712123669384f
Make sure that the native component of WebView has been initialized
before any native-level optimization involving window focus occurs.
Change-Id: I24ca5fe21657aeb1a1faf5bc36fba5ea11064f86
This prevents animations and other live page content from consuming
too many resources while the user is interacting with a popup window.
Bug 5300522
Change-Id: I40fb6d16d56b540c431172052a1ae7fead7109be
Reset the text wrap scale to the correct value (i.e., reading level
scale) on zoom to overview. This addresses the scenario where text is
wrapped at a larger scale following a pinch zoom and double tap to
reflow.
Bug: 5254253
Change-Id: I57f706ef4254dd3f194cc35f109dd48b61b72f73
Use the URL host and path rather than the complete url to store
form autocomplete data. This helps in the situation that a site
uses some dynamic query string on the page that contains the form.
Also set the autoocmplete threshold to 1 so that we don't flick the
autocomplete options up and down as you type the first few characters.
Bug: 5265606
Change-Id: I7b372400062ae34f70a78b786007910dc179b101
bug:5255022
bug:5218838
When the view starts scrolling, we tell native so it can block updates until the
view stops scrolling. This change fixes an issue where wouldn't tell native that
we stopped scrolling because the view didn't have room to move.
Change-Id: I5f2eec31493570937f7b8b2992a85283de06fb60
Bug: 5239166
Turns out nativeRecordButtons is necessary even if we are not
using the native selection rings.
Change-Id: I8e7713928b77c0098640b51ce8e8815dad0c9545
On a double tap, zoom to either reading level scale or 0.5f more than
current (overview) scale, whichever is greater. This addresses the
scenario for large screen devices where overview and reading level scale
are the same.
Bug: 5165527
Change-Id: I50216d60f98b2904f06742336b9c8c7c512328a6
To improve WebView app startup time, preload libchromium_net which
was recently split from libwebcore into its own shared library.
Bug: 5112647
Change-Id: I4417d5a4f8c7783e8fa7b8eaddf89aaeb3693fac
This enables apps to make use of the system's visual edge effect used
during overscroll in 2D content.
Also un-@hide the getCurrVelocity methods from Scroller/OverScroller,
without which it becomes cumbersome to obtain values to pass to the
EdgeEffect#onAbsorb method.
Change-Id: I40e452455f5cb5d45d1fb3687f739fc8eae65560
* changes:
MediaDump: use the MediaPlayer#setSurface method
HTML5VideoView: switch to MediaPlayer#setSurface
MediaPlayer: unhide the setSurface method
Surface: unhide the SurfaceTexture ctor
This change updates HTML5VideoView to use the new MediaPlayer#setSurface
method rather than MediaPlayer#setTexture, which is going to be removed.
Change-Id: Ia4c8c822bd4735caf95f3f295485d60f016577c1
Bug: 5220835
It is possible to call setProperty before webcore has initialized.
In that case, the content invalidate is unnecessary as there is no
content to invalidate, so just ignore the request.
Change-Id: I52471a1739443ba8f1e514a5908678552246d80b
pass isScrolling info to glwebviewstate
pause webkit in a way that doesn't require full inval on resume
depends on change https://android-git.corp.google.com/g/#/c/130210/
bug:5106313
Change-Id: Icbe57e3a163c17c99bd1ea49ab42e40f9d41cc6d
