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
WebViewClassic created the CookieSyncManager instane as a side effect of
starting up its internal WebCoreThread. As this forms part of th API
contract (app doesn't need to call CookieSyncManager.createInstance if
it already made a WebView instance) promote this logic up to the API
layer.
Change-Id: I0e92d97be987dfef90162ad379c79b066aae34e0
In order to increase test coverage, reset to the default value everytime
the build ID changes.
Bug: 10427705
Change-Id: I75e301d26ee0ca52265c5f7fe48661787b596168
Cherry pick of master I210dbab01c8b8d1eeff316a23c5d011e2e6c2a74
This exposes the super_onDrawVerticalScrollBar method which will
be called by the WebViewChromium implementation.
Change-Id: I3fe348633c163514e67b7712f1e9a086dee3d338
Bug: 9773865
This will not be visible in shipping config, so shouldn't be a major
source of log spam.
Change-Id: If09734b70e59aeab87c6dddee72212aa6748505f
In preperation for DEFAULT_TO_EXPERIMENTAL_WEBVIEW flag-flip, make this
field and WEBVIEW_EXPERIMENTAL_PROPERTY private so we know all users are
querying the property in a consistent way.
Change-Id: Iabaffb8ac5a34e323b170339d47f872eb4c83042
In preperation for flag-flip, have Settings app access the current
state via methods that are neutral to the on/off state.
Also setup the property to change name when enabled by default, to reset
any user changes to this setting.
Change-Id: I55017bcd89573c1ecac7de8913264d9cf66fdcd9
onMeasure is not deprecated, this tag is spurious (and has no effect on
the api.txt or SDK anyway)
Change-Id: Iae003727649e86db2e0adaa5071399b676526c38
This API is intended to replace the "WebView.loadUrl("javascript:...")
pattern that is the current mechanism for executing JavaScript in the
context of the current page displayed in the WebView.
The new API is more convenient - it doesn't trigger the normal URL
loading path - and so does not have side effects such as hiding
the keyboard - and allows the caller to specify a callback that will
be invoked once the script execution is complete.
BUG=9814043
Change-Id: I3f27e8ff5371077d9265430090d61381a3a86e76
This is needed to make use of the new Accessibility implementation
in the Chromium WebView. nos for WebView Classic.
Change-Id: I96bd2426d2de3b26dc9b72d0fdbacefa9bbe20f7
This is needed to make use of the new Accessibility implementation
in the Chromium WebView. nos for WebView Classic.
Change-Id: I8e26035d15af494e4caa50b4c6c7cb4ac8efeb9e
Allow the appropriate WebView to be preloaded in the zygote by
constructing the currently selected WebViewFactoryProvider when the
WebViewFactory is preloaded. At runtime, if the preloaded provider is
still the current selection, the preloaded instance is used, otherwise
the provider is loaded at that time.
This change also removes "graceful" fallback from the experimental
WebView to the classic implementation: if the option to use the
experimental WebView is selected and it could not be loaded
successfully at the time a WebView is created, an exception will be
thrown, rather than allowing execution to continue with the classic
implementation, as the fallback may mislead developers who do not
examine logcat output in detail.
Change-Id: I0cd01c784d7048abeac55ab5863ca16b8fd9ecf2
The new webview.force_provider property, when set, enforces the use
of Chromium or classic WebView, regardless the value of the
persist.sys.webview.exp (accessible through the settings UI).
This will help telemetry tests to run correctly regardless of UI
settings.
Change-Id: Ica5a0faa7f7539c22332cac5a8946f11fb7df6b2
Use the ordinary system class loader to load the Chromium-based WebView
implementation classes now that the implementation .jar is part of the
boot class path. Instead of checking for the .jar file's existence, just
check to see if we can load the class to determine whether the new
WebView is available.
This also removes the check for Build.IS_DEBUGGABLE; the Chromium-based
WebView will now be available in user builds if enabled in the developer
options.
Change-Id: I06bae9b91656aa41b09c0e6f63f90736db993418
Alternatives are advised in the JavaDoc. The settings will be marked as
deprecated in the K release.
Bug: 9004875
Change-Id: I033be03f14244390016cb2b40337aab1df945465
