Bug: 6108346
Highlight now correctly doesn't show up unless it is a click, and
no longer has any weirdness with sticking around unusually long
Change-Id: I06f6eae45d970085232466f17cbbd9ebaefc4d69
Bug: 6407623
If script injection is disabled, the accessibility injector works
by modifying the text selection. However, this would cause WebView
to go into text selection mode, showing the CAB and such, which
we don't want. Add a flag saying WHY text selection is being changed
so that we can respond accordingly in WebViewClassic.
Change-Id: Ia509def3fcdb022b93fbbc7ed89bc9558663afd3
Removes no longer supported splitPicture
Removes unnused code
Bulk of the change is in webkit CL: https://android-git.corp.google.com/g/#/c/185850/
Change-Id: I4eca363ba3cb4a6d6fccc82bf5ea8588df780a4b
WebViewDatabase has a getInstance() method, so similarly
to WebStorage, WebIconDatabase etc we refactor it into a
proxy class, and move the current implementation into
WebViewDatabaseClassic.
Also clean up some JavaDoc in touched files.
Bug: 6234236
Change-Id: I71cbd8f78e60f396e96e8546073ad634797cce15
This fixes the JavaDoc style for the following classes ...
- CacheManager.java
- CookieManager.java
- GeolocationPermissions.java
- WebResourceResponse.java
- WebSettings.java
- WebStorage.java
- WebView.java
In particular, this applies the guidelines at
https://wiki.corp.google.com/twiki/bin/view/Main/APIDocumentation
This should help to ensure that future JavaDoc comments use correct style,
rather than using incorrect style for consistency.
Note that this change does not attempt to improve the content of the JavaDoc
comments. This will be done in later changes.
Bug: 5461416
Change-Id: I79e9b15a8cf3597195d58e154a7eb1bcc462944c
This allows CookieManager subclasses to correctly override all behvaior
in the base class.
Bug: 6379925
Change-Id: Ife02db24bc192bc1eabf09e0d64668716786d237
Bug #6365056
WebView enqueues a functor in the hardware renderer to handle
animations and this functor is called at a later time by the
hardware renderer. However, the functor was not removed from
the queue when WebView was removed from the window. This could
cause the hardware renderer to attempt to execute an invalid
functor and lead to a crash.
Change-Id: I9d38e80f3fdc5e29d4d0cdfa1e893c251a954508
This is a quick workaround to get tests running again, will follow up with full fix tomorrow.
Bug: 6379925
Change-Id: I96d6e27bfb8f8cd41ec08845ab0fb1e584dbc9da
There are times when we deliberately put the WebCore thread
to sleep (i.e. waiting for a user to complete a JS prompt or
dismiss an alert). In this case, we don't want the WebCore thread
watchdog to fire. Pause the watchdog before we put the WebCore thread
to sleep and resume it again when the thread wakes up.
Factor out the repeated send/pause/wait/resume code into it's own
function.
Bug: 6366520
Change-Id: I17ecf9d466ce21b25a9e5cb8ff4cb0e5fab7605b
GeolocationPermissionsClassic
CookieManagerClassic
WebIconDatabaseClassic
WebStorageClassic
Also creats a WebViewFactory top level class - this remains hidden
for now, as it's currently only used implicitly by the other
public WebView classes to create the provider instances.
Bug: 5626244
Change-Id: Id0ca1c16d8058f31a86414bbc0e8a55db4b907ba
