| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Delete all the Java classes used only by the old WebView implementation,
and also sections of common classes that were only needed for the old
WebView.
Bug: 10427705
Change-Id: I02549a71104b35d86d99058c71f43e054730ec7d
|
| |
|
|
|
|
|
|
|
|
| |
Fixed one setting that was migrated but not marked deprecated.
Removed a hidden setting that is no longer used by the new
power manager service.
Bug: 7231172
Change-Id: I332f020f876a18d519a1a20598a172f1c98036f7
|
| |
|
|
|
|
|
|
|
|
| |
Several of these are duplicated; referring to a single source makes the code
paths using them easier to track down.
(also removing a spurious import)
Bug: 6237833
Change-Id: Ibdacc124c047e37c7f0ced9ecc6f26ae3e6b4326
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All future releases will use the Chromium HTTP stack and maintaining two HTTP
stacks adds maintenance overhead. The Chromium HTTP stack requires V8, but we
now use V8 in all build targets (b/5495373), so we can safely drop the Android
HTTP stack.
LoadListener, HttpAuthHandlerImpl, Network, SslErrorHandlerImpl, WebViewWorker
- Android-stack specific, removed
StreamLoader, FrameLoader
- Require LoadListener, removed
CacheLoader, ContentLoader, DataLoader, FileLoader
- Extend StreamLoader, removed
BrowserFrame
- Removed methods that create LoadListener
- BrowserFrame.startLoadingResource() is called from native
CallbackProxy, WebView
- Removed calls to Network methods
CacheManager, CookieManager, CookieSyncManager, WebViewCore, WebResourceResponse
- Removed other Android-stack specific code
JniUtlil
- Removed useChromiumHttpStack()
WebViewDatabase
- Removed all code to create cookies and cache databases for Android HTTP stack
See corresponding WebKit change https://android-git.corp.google.com/g/166327.
Bug: 5495616
Change-Id: If491675516f6eb187077af4220214bb6e6a8d045
|
| |
|
|
|
|
|
| |
Need the context to get the package name, adding it method here
that can be called from JNI.
Change-Id: I530d81d9d922ea73a3f9d185618a5c4cfde0aca7
|
| |
|
|
|
|
|
|
| |
JniUtil now returns empty string instead of crashing
when the OS can't find/create a cache directory. Have only
seen this happen when the whole file system was broken.
Change-Id: I867017d62dce83cae3e83959eac9e974433bbdc9
|
| |
|
|
|
|
|
|
| |
Variable is not needed, and removing unneeded check
Also throwing an exception if sContext gets set to null.
Change-Id: Ic61ba4c88a162eb730e166f0e9f477e809b51f42
|
| |
|
|
|
|
|
|
| |
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 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
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
load it
Bug: 4584468
Change-Id: Ib553cda843669d40cc52ff0bc84bea2c626c5045
|
| |
|
|
| |
Change-Id: I386aef25010c95b15fb6a8edc96e59e538540306
|
| |
|
|
|
|
| |
Part of fix for bug 2862096
Change-Id: I91f7e7aa1f0fef10b1617e91a167594d4de41b71
|
| |
|
|
|
|
| |
Part of fixes for bug 2862096
Change-Id: I86f1255c17efb367fac54b69b8de220d2874fc70
|
| |
|
|
|
|
|
|
|
| |
Context from an Activity are not meant to be store past the
lifetime of the Activity.
Fix for bug 3306898
Change-Id: Ib2f12cbdc3ec8aa0a6adf4770e6be4569fa6402c
|
| |
|
|
|
|
|
|
| |
Dolphin crashed when sContext.getCacheDir got called too early.
This was because the let the user choose to use sdcard or
internal memory, and the choice was not yet made.
Change-Id: I8b3ba260c26233c6459efbb9e5e50fad2260a24d
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is a generally useful method, not specific to CookieManager.
I want to use it to modify the behaviour of CacheManager when we're
using the Chrome HTTP stack.
Corresponding C++ changes in I78a92cb2
BUG=3270236
Change-Id: I56b0ddcaa93ef340f4ffc3578486c3c96316f2ec
|
|
|
The reason for this is that the CookieSyncManager might not be
initialized right after a webview is created since the initialization
is done with a message.
If someone creates a webview and tries to access a cookie right
afterwards that would cause an unintended exception.
This requires a change in external/webkit
Bug 3172863
Change-Id: I4f4f162253e2af09f63ee582bfce9f75ccf4037b
|