The TTS instantiated from here shouldn't clobber any
existing TTS objects opened within the same package context.
Ideally, the TTS API should work fine with multiple TTS object
instances within the same package context but making that happen
correctly is a larger change.
bug:5659758
Change-Id: Ia1f63c61b9f12ac92ff42a427a004d414e42a759
In the hardware accelerated case we were not updating webkit
with the new zoom information. This was causing plugins to
render at the old zoom level.
bug: 5663981
Change-Id: I3cb18ad9ca4f185f384ea9fb68780f29160391ad
When the WebView is paused, or another action (such as navigating to
a new URL) occurs, cancel any ongoing <select> tag dialog that is open.
Bug: 5666545
Change-Id: Ifc35a239b729ed93cbf82b2096334f7d63f8993d
Bug 5342918
The content rect of the WebView was being retrieved during
the draw while the viewport rect was being set when the
draw functor was setup. During animations, the content
rect was changing between the time the draw functor was
retrieved and it was executed. The content rect is now
being set with the viewport rect.
Wekbkit Change: I05d68dcc
Change-Id: I1b0978eeb27d9f1deddfeba3ede869f735f74394
Updated WebView documentation to clarify this behavior.
Additionally, if target-densityDpi is specified in the meta viewport
tag, update the display density in ZoomManager.
Bug: 5477652
Bug: 5327492
Change-Id: I176e87489f76a2ee6595d76a006e302b07595de1
Bump WebView database version to 11. This has the following effects:
- Removes the old webview cookie table on GB devices. Cookies are now
managed by the Chromium stack.
- Removes the old webview cache database on GB devices. Cache is now
managed by the Chromium stack.
- Autocomplete form data is now stored/retrieved based on
the URL minus the query string/fragment. Upgrade any existing
form URLs in the database to match this format, so we can
still use them. This will impact GB and HC devices.
This has an unfortunate side effect that we may end up with
duplicate URLs in the formurl table (say we had two URLS for the
same host but with different query strings). Currently we only take
the first url from the table - which is fine when they were
unique. The simplest way to work around this is just iterate all the
rows returned and use all the values we find.
Bug: 5560410
Change-Id: I59323dc5e523969e0a1c268b5936d6fa998d625c
Bug: 5533078
There is no alternative and this is still useful and used. It should
not have been deprecated.
Change-Id: I641026cf76ea87738909827b7c48a556d9021d11
During upgrade from v9 -> v10 the database version was not
being updated.
Also remove conditionals based on what are effectively hardcoded
truth values to simplfiy the logic greatly.
Bug: 5560410
Change-Id: I31a01aa35a109a951d4e4c6d5b884bb666668b28
Bug: 5533389
Treat layer scrolling as a no-op scroll by calling
onScrollChanged with old scroll == new scroll
Change-Id: I1dc2b94b37c65bf088806b8d28be32883e3b8bee
Bug: 5601629
References tend to always be equal to the things they are referencing,
use copies instead.
Change-Id: I0827878e91ef1fa6e0abe2d6499d55f4a211d890
Bug: 5594608
If onPause is called or if the view or view's window is no longer
visible, pause webview drawing. Calls to onDraw will continue to work,
but animations and other continual drawing will stop
Change-Id: I11640f087852d1a9a33b945ff72297fab1d25b94
Bug 5268793
Webkit knows about the correct initial position for web pages.
On initial show, scroll to the webkit position.
Cherry-picked from master CL: I2537b84a
External WebKit CL: I6a91b97f
Change-Id: I2537b84a30a26a79a8a0f23fe62b9ed757f9c5a4
Fixes bug 5544556: All email content is wrapped prematurely.
Previous change (I5a22dd20) didn't take a few other cases of
mViewScale>0 into account.
Change-Id: I4f9578f3558f026c472492ac07d19004416dc228
In any case that the HTMLVideoView is recreated with no GL texture, we should
recreate the GL texture to make sure we always have a valid texture ID.
bug:5530006
Change-Id: I703a987a7530dbeef74e502f3c9ff329beca8c4e
Reverted changes made to fix bug 4982074 (Book text display is limited
to about half the available screen.) The Books app sets initial scale to
100%, and since display density for Crespo is 1.5, initial scale was
actually being set to a smaller value in Device Independent Pixel units.
The correct fix is to take display density into account. This fixes bug
5477652: webview scale factor wrong on prime in reddit app.
Change-Id: Ie09172629add7fb28ca6b47d0fd8f6450c5df569
