Bug: 7073422
Create the plumbing to use an annotation to allow access to
inherited methods of jsinterface objects. The default webview
behavior has not changed yet. However internally an a flag is
introduced to restrict javascript access to methods that have an annotation.
Change-Id: I41927248e6bc4b09d17c0707c60fe5e6ab681e66
Bug: 6961494
Don't call clearHelpers in destroy(). It is already called
in onDetach, which is where it needs to be. It can't be
called by the finalizer
Switch onCancel listener to onDismiss listener. Fixes an issue
where destroying can live the webcore thread hung because onCancel
won't be called, but onDismiss is
Change-Id: I669c389c8c9a81d92c27f88d83bcb711c6c0a5ee
Bug: 7073422
The feature that is using search box implementation was removed from
browser after Honeycomb. This is to remove the js interface that
is added for this feature.
Change-Id: I9441d461caf189467e4ad45de958c13b81f4ff17
The AlertDialog creates in onSavePassword method leaks if
WebViewClassic is destroyed when the dialog is shown.
Change-Id: I81f20e1dd138467a6413766c0a081b389b334ae0
Allow WebViewProvider implementations to subclass SslErrorHandler
but at the same time maintain API compatibility by @hide'ing the
constructor.
Bug: 6238802
Change-Id: I5de268364ed74e59f62439b8612ab682656a7906
The Chromium WebView Provider needs to subclass HttpAuthHandler
so that we can adapt a ChromHttpAuthHandler into an
android.webkit.HttpAuthHandler. Currently the constructor (that
does nothing) is package private. So to satisfy the subclass
requirement, make it public, and to satisfy the API, make it
@hide.
Bug: 7034995
Change-Id: I9846aecacce078696db5be709394afb980eb25a6
- no need for WebSettings to bounce via WebView to get to the factory
- move this static (non-factory) method into the Statics inner class.
Bug: 6329117
Clean cherry pick: d1c4faa5a4
Change-Id: I96807df0171c7308421ca8811cfcb1bf710cb007
TextSize is deprecated, so we wouldn't expect from WebViewProvider
implementations to re-implement it in some other way than Android WebView does
it. This also makes recently added TextSize.getValue method redundant.
Clean cherry pick: 1202d66f78
Change-Id: Ib6aecb187f10ac3ec5d12cb839cb814ec0c564fe
Bug: 6635437
Fix onGenericAction to support scrolling layers.
Calling startScrollingLayer detects if there is a layer under
the mouse pointer, and if so switches to DRAG_LAYER_MODE. Then, calling
doDrag will correctly handle scrolling the layer in DRAG_LAYER_MODE,
switching out of DRAG_LAYER_MODE when we hit the end of a layer, and
scrolling the page if there isn't a layer. It is the method used
by the touch drag path.
Change-Id: I00be09a63c40caa8fce94134c57db0894a62fef0
Split WindowManagerImpl into two parts, the WindowManager
interface implementation remains where it is but the global
communications with the window manager are now handled by
the WindowManagerGlobal class. This change greatly simplifies
the challenge of having separate WindowManager instances
for each Context.
Removed WindowManagerImpl.getDefault(). This represents the
bulk of this change. Most of the usages of this method were
either to perform global functions (now handled by WindowManagerGlobal)
or to obtain the default display (now handled by DisplayManager).
Explicitly associate each new window with a display and make
the Display object available to the View hierarchy.
Add stubs for some new display manager API features.
Start to split apart the concepts of display id and layer stack.
since they operate at different layers of abstraction.
While it's true that each logical display uniquely corresponds to a
surface flinger layer stack, it is not necessarily the case that
they must use the same ids. Added Display.getLayerStack()
and started using it in places where it was relatively easy to do.
Change-Id: I29ed909114dec86807c4d3a5059c3fa0358bea61
Bug 6329117
Add ability to get the default user-agent without creating
a WebView. The method is implemented for WebSettingsClassic.
Change-Id: Id15fb57f65875752ccf644481a22b88644635f5d
This seems to have been incorrect since this code was first written for HC. I
can only think that the error was made due to confusion between portrait and
landscape mode as development switched from phones to tablets.
Tested on stingray and prime.
A similar fix will be required for Chrome.
Change-Id: I5da13c489fdb9de340b9e6ea8868c9f1adc15bb2
Bug 6803309
When the alert dialog raised by the JS unload handler was pressed
outside the alert region, it was canceled and no response was
sent back to WebViewCore. This captures the cancel event so that
WebViewCore doesn't hang.
Change-Id: I0c125e759a252a803c2c77aa9533adef7fa82d3d
Bug 6854156
setComposingText is in the middle of a batch and it was resetting
the InputConnection. When the batch ended, it was closing a
batch that wasn't open on the new InputConnection. The reset
turns out not to be necessary anymore -- the LatinIME respects
the content when setComposingText fails to change anything.
Change-Id: If3352b32ed7b3c90c8dcb3d5ff8d308e82849d85
* commit '7c00f81606de1880c3f28e54cea064c3b90da3e7':
docs: fix a bunch of links from javadocs to api guides and add some attributes to Spinner and Switch
