Bug 11291911
These deleted classes were previously public APIs and so need to remain
in the build (but hidden) in order to keep existing apps working.
(Partially reverts Change-Id: I02549a71104b35d86d99058c71f43e054730ec7d)
Change-Id: I28e53b056f41e66645136f5e18fba2ff55a65fe5
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
WebViewFactory remains as an abstraction layer, but will now always
creates Chromium WebView instances.
Bug: 10427705
Change-Id: I045e43eb35462567fecd29d04e7b61902baef547
Follow up to Change-Id: Ibc2496d5cef97b4685e001086f712fcaac231024 - this
method did not exist in klp-dev branch.
Change-Id: Ie64dd3b2357e0abefb4c7d3492f02d23d347f89f
So long as all usage is from a single thread per instance it is OK if
it's a non-main thread.
(But note that for apps targeting JB MR2 this was enforced to be the
main thread anyway).
Bug 10937207
Change-Id: Ibc2496d5cef97b4685e001086f712fcaac231024
Add a workaround to ensure that the WebViewDatabase and JniUtil can
still be initialized as side effect of making a CookieSyncManager
This was collateral damage from the fixes for Bug 10932261
Change-Id: If5ba65a7822d5b0afc14139dd84125058bf96897
Bug 10932261
Most of this flow exists purely to get the Context from
CookieSyncManager.createInstance over to WebViewDatabaseClassic. Make
that depenency more explicit (with a TODO to remove it) and this allows
a much simpler CookieSyncManager implementation for the normal case.
Note after this patch, CookieSyncManager.getInstance() is technically fine
to call without a prior call to createInstance, but retaining the
ordering requirement as a convenience for anyone developing on new OS
but still supporting the older versions.
(Note that CookieSyncManager instance is not required for correct
operation of either existing webview, so these changes only impact
the public API contract of object lifetimes, not the underlying
implementation)
Change-Id: I51fdd6622704f1c749277fee6df2f84ac4c704d2
Simple resolve: two new methods added to same class.
Conflicts:
core/java/android/webkit/WebViewFactoryProvider.java
Change-Id: Ic8b26f2a51279348b19a9c5b30d492f67d62ca81
Bug 10361803
exportToPdf use-case not supported in K so removing that dangling
reference from the javadoc
Change-Id: Ia0fe3aa9ed5150639d1f72341c89568a0a7e1c7d
Bug: 10361803
Bug: 8565831
Several obsolete APIs now deprecated.
TEXT_AUTOSIZING can now be unhidden.
Change-Id: Ib0afa4bb010f35816d3b9dd3695e8997f0ff0793
This particular helper function is being removed from NativeCrypto, so
move it here as it's the last user of it.
Change-Id: Iea13ba499487d838068d6156d4d1e6861d05eb36
Bug:10652036
Change-Id: Ibcc7e48f4e4ce1bc437c0d3fb89d3d66a90dca64
This is a cherry-pick of a5c86c644b
to prevent a automerger failure.
Conflicts:
core/java/android/webkit/WebView.java
core/java/android/webkit/WebViewClassic.java
core/java/android/webkit/WebViewProvider.java
This adds static (as this is for the whole process) method
for controlling the web debugging state.
Please note that the implementation only makes sense for
Chromium WebView, and it's a no-op in WebViewClassic.
BUG=8691809
Change-Id: I815b4d69ad9ee814ca4cec1da81490b63ba2da68
