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
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
According to CTS tests (WebSettingsTest.testLocalImageLoads),
local images access is allowed regardless of the state of
AllowFileAccessFromFileURLs.
Bug: 5461416
Change-Id: I71f5c38a6b0f3720c8c369c0e19f379c78ace06f
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.
Change-Id: Ia9d0c743424be0727be6d5df6c7da30514d621b7
It turns out that the BROWSER_TEXT_SIZE_CHANGE event isn't listed
in google3/wireless/android/production/checkin_config/root,
which means that statistics on it isn't collected, so the logging
statement doesn't have any useful effect and can be removed to
simplify code.
Change-Id: I66d694cdb13e677bb979f5e962ed2cc8d743bdec
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
After the switch to the Chromium network stack, this setting is
effectively the same as LOAD_DEFAULT, and having two settings
with the same meaning is confusing.
This change is blocking https://android-git.corp.google.com/g/205883 in CTS
Change-Id: I02cc23477f107e7f4cec37dcbad4f25503b5e840
As the 'value' fields in these enums are not public, it isn't possible to
retrieve the enum value if the WebViewProvider implementation is defined in a
different package to the API. Adding public hidden methods to fix this.
Change-Id: Ia5fb1332d0043e127b4bad03a295d8abf1a5e5b9
* commit '7c00f81606de1880c3f28e54cea064c3b90da3e7':
docs: fix a bunch of links from javadocs to api guides and add some attributes to Spinner and Switch
Currently, WebViewFactory is hardcoded to always load
android.webkit.WebViewClassic$Factory. This change allows us to
load the Chromium powered WebView by setting the
"webview.use_chromium" system propery to true.
Change-Id: Icebfc4d5c4a61230c5e5dccac1ec5eca59f650ac
