Previously we save the state in Java side, but it is better to check with
native side since the exact state is already there.
This will help to get the updated state from javascript too.
bug:5765848
Webkit side change:
https://android-git.corp.google.com/g/#/c/157866/
Change-Id: Id0316b694c1597b50a1c3b123b31efc6b0fac706
This issue was found while investigating b/5328288.
After navigating to a page that specifies target-densitydpi in the
viewport meta tag, this density value wasn't reset to the default value
for a page that didn't.
Change-Id: I1a66dab769026367224ecf4cc28bc033ee97e475
Bug 5806859
Bug 5795341
Add a custom InputConnection to capture the deleteSurroundingText
command and use it to send delete key codes to the WebView for
single deletes or calling into WebViewCore to delete contents for
more complex changes.
Also makes the IME options "normal text" for webkit-based text
entry.
Webkit change: Ic938d6fa
Change-Id: I18606014a034194928a61981dc3e2400a7db5fac
Run a background "watchdog" thread that will check for
the WebCore thread stopping processing messages (this
can happen if a piece of JavaScript goes into an infinite
loop, for example) and offer to close the WebView app when
it detects such a case, much like the normal system ANR.
Bug: 2563868
Change-Id: Ic74813b1e630d657c340a7017a4b0814071eb041
Bug 5827817
Added a nativeClass parameter to all appropriate JNI methods
and used it instead of GET_NATIVE_VIEW to reduce JNI overhead.
Webkit Change: I02004fe1
Change-Id: I49c7ecfd598826ffe78067aab393a24860ce10ef
- we can do this, because HitTestResult never had a published constructor
so the only code that can create it has always lived in this package.
- doing this makes the class design cleaner, and smooths the way for allowing
the new WebView implementation to deal in these results in contexts where
the appropriate WebView instance is not readily available.
Change-Id: I9e1f1c0faeb16436b1861aab3c2871a5851dfb54
Most of these APIs have no intention of being published, at least not in anything like the current form.
Change-Id: I1df3ae00320f909caea8a0d42d50ee7400577635
The bulk of the change is in to external/webkit:
https://android-git.corp.google.com/g/155448
This part of the change simply adds some optimizations to avoid syncing to
native when not required, and cleans up the JavaDoc.
Bug: 5745181
Change-Id: I0009c1868755fe211ec2dc31bd007d393aabfbe3
Bug: 4586251
Original CL was for ics-mr1. We decided it should be in master
instead. Original CL
https://android-git.corp.google.com/g/154083
Current ssl cert logic makes callbacks to webkit from the
UI thread. This is not right. Move the callbacks to proper thread.
Change-Id: Ie3de7dbaed7780dbb6cf537ca1d29686d867b784
Fixes bug 5726043 (Extra double-tap needed to zoom out to overview mode
on nytimes.com on a Stingray)
Change-Id: I54dc303f4aa81ddc38c234228adc915b9f6749dc
The URl from which to inject a screen-reader for WebView accessiblity support should be
configurable because: 1) The accessibility engineering team should be able to point
devices to a staging build of the screen-reader; 2) We would like to be able to change
this URL via the Google services mechanism.
bug:5718543
Change-Id: I3d4d343f1c93e0e0173f04b2912949fe8a3566b9
