Bug: 6656538
Due to the WebView/WebViewClassic refactor we need to call
WebView.performLongClick instead of performLongClick directly
to allow subclasses to override performLongClick
Change-Id: I9b580217fbafc82d03e63eabfdda9f5bad98db0f
Bug 6590742
Separated base and extent handle alpha so that they can
be hidden individually. Added visiblity check and animations
to show and hide the handles.
Change-Id: I08ce7f870bbb8e059550797afa18c2db39394caf
Last remaining bits:
- push JNUUtil.setContext call down into WebViewDatabaseClassic
- remove references to hidden ClientCertRequestHandler from the public API classes.
Change-Id: I9605dc2493b73fe8f22c7bb38c73d36632e0c7fa
Bug: 6628376
The issue here is that contentX & contentY can both be 0 if we are scrolling
slowly enough as they are adjusted by the page's scale and can thus round down.
However, this would result in us falling out of layer drag mode even though
we haven't tried to scroll past the edge of the layer. Detect this case, and
stay in layer scroll mode.
Change-Id: I3c655d0d03e8f89887abbe718bd24699c133ee1a
Bug: 6569073
Only nativeDestroy and nativeStopGL need to be called on the UI thread,
so split up destroyImpl into 3 functions, and only have the native
destroy be pushed to the UI thread if necessary. Also make the work that
is delayed be static without references to the finalizing WebView to allow
it to be fully deleted immediately after finalization.
Change-Id: I4e424051e69df0bc409af95ca3f3d2b9e58a6b75
On a page load, the (viewport) metadata settings for the main frame are
reset. Reloading a page with viewport meta tag specifying target density
dpi will result in 2 back to back update zoom density messages to be
sent from WebViewCore to UI thread.
In setupViewport(), remove update density messages in flight. If the new
density is indeed different from WebView's default scale, queue another
message.
Bug: 6509512
Change-Id: I195e40277bf1bcccb0e61d84ed84db1e34556243
Bug 6557816
Change text selection to modify only the base or extent, not
both points of the selection.
Webkit Change: I9a08633160eeb14d5c45246c6128aa02c1642e8d
Change-Id: I355b21e9062b5d364cfb278fda239a4ecdff16d1
Bug 6557816
This is a step in preparation to fix text area selection.
It moves selection from left/right to base/extent. left/right
can cause problems when dragging cursors -- it is sometimes
difficult to tell which cursor should be dragged, the left or
right, but we can always keep the base/extent constant.
Webkit Change: I5609d07ea2ee67fc08d15cfcad31f49302f33297
Change-Id: I2f9b963e93bb1ab86a9b26518fca52449b56d5d9
Rather than caching the WebViewDatabaseClassic instance in a member,
grab the instance when we need it.
In the case of WebSyncManager - neither it or it's subclass uses
the WebViewDatabaseClassic (and it's subclass is final) so remove
it's initialisation. We must leave the member declared however
to satisfy the published API.
Bug: 6482144
Change-Id: Ibf5186a2851d17f5ad62b35ad543aeadff5618d9
Functor attach should always be successful, but adding a fallback just in
case. Also invalidates the WebView on initial content arriving.
bug:6511995
Change-Id: Ibca16505afec9f693ea4a7cc4966cd6d7353725c
This method was only supported with the JSC JavaScript engine.
V8 became the default JavaScript engine in Froyo and this method
has not been invoked since. Support for building JSC was removed
in b/5495373.
Bug: 6295376
Change-Id: I3dbe83f375b88ebbbb713d3c3fa5a2fa323a0d45
