WebViewCore.java: add a MotionEvent field into TouchEventData for multi-touch so the extra data such as pressure, size can be preserved.
WebView.java:
1. Extracted the common code for multi-touch and single touch to a new private function: handleTouchEventCommon()
2. Extracted the multi-touch code, including zooming and panning, to a new private function: handleMultiTouchInWebView()
3. In onTouchEvent(), single touch events keep the code path, but multi-touch events are always passed to Webkit first.
4. In Privatehandler.handleMessage(), if WebKit didn't consume the multi-touch event, the private handler calls the handleMultiTouchInWebView() to zoom and pan.
Change-Id: I3eba8812bd7cf6a298ff12e0b66223dae6725060
Bug:3329956
Also ensure that keys dispatched while the WebTextView
is attached get sent to the WebTextView.
Change-Id: Icd9125a85929089a6f376b71c1cb40e885264168
Bug: 3211038
The building of the user agent could previously have multiple sequential
spaces. This was causing the CTS test to fail.
Change-Id: I13fc76ba6b97ee84dd44461b4d03b6ca70b48cdf
Make key accceleration exact; if alt is required,
allow only alt, and so on.
Also, set the touch point when nav'ing with the arrows
or trackball so that context menus have a point to
work with.
bug:3301564
bug:3241968
Change-Id: I574ce145941e84ac0934efd323d9db71eec11663
Compute whether the initial tap point is in
a scrollable layer or not. If it is, get
the bounds of the scrollable layer and use them,
clipped to the view, to determine when the
select anchor is dragged close to the layer's
edge, to invoke autoscrolling.
Fix some bugs around stopping the autoscrolling
when there is nothing to do, and when a motion
up event is sent.
requires companion change in external/webkit
bug:3191699
Change-Id: Ic9229b063a8102ec93d0cd5bcaba774cc170c106
1. Added a mechanism to select the cursor ring content if accessibility is
enabled - This is achieved by sending an event to the WebCore thread
(if accessibility is enabled) to select the content of the cursor when
the latter moves. Added code in WebViewCore to select the given node
and notify the UI thread for the selection markup which is delivered
of the accessibility injector which manages sending accessibility
events. This is relevant for adding accessibility to WebView if
JavaScript is not enabled. (If JS is enabled we inject a screenreader
written in JS).
2. Fixed the event delegation to the accessibility injector since it
should be able to consume key events of interest and perform some
action which leads to sending appropriate accessibility event.
In the previous implementation it was possible that the injector
consumes the event but the latter was bubbled up.
3. Added function to scroll the selection into view while moving it
around based on user commands.
Note: This is a part of two project commmit.
Change-Id: Ibb81d0468726efbe3bf6e3add1b19c69e3206638
When using the Chromium HTTP stack, most of the calls to CacheManager
methods are not required, as we're not using its cache. These methods
are now marked with asserts to make this clear.
Also avoid creating the cache database in WebViewDatabase.
This will avoid creating the database databases/webviewCache.db and
the directory cache/webviewCache.
Bug: 3270236
Change-Id: I68f94dde16830ed817454d5e1af961f41b71d018
This potentially helps the following issue. But anyway, this change
is good to have.
issue: 3292648
Change-Id: I0ad74b802d7ce2c3d66de8115187638f1d5e72ff
If the cursor is active and on a node that doesn't want
key events, treat the enter key as a click.
Otherwise, pass key down and key up to webkit.
A companion change in external/webkit adds frames
as nodes that wants key events.
bug:3325093
Change-Id: I134d2999505925ee1e571841759cb295103b5a30
Refactor zoom overview width calculation in FirstLayout and NewPicture;
also taking care of the case when wide viewport is not enabled.
This fixes the setInitialScale Cts test case, which is broken by some
scale related changed for fixed viewport browser.
issue: 3242034
Change-Id: Ie54d089763ee38029ef25e6029884a17c2135f97
Bug:3312049
Do not start Find on page if the action mode fails to
start. Clean up showFindDialog.
Requires a change to packages/apps/Browser
Change-Id: I204315665d3bf9f3ac78e78c4059c5a6f24695db
Allow the hosting application to do what they want if the
control key is pressed. In particular, let our Browser
map Ctrl-arrow to back and forward.
bug:3270434
Change-Id: I2dfa648edbf5a0e48b674df5023182b4a70985f6
Treat the numeric keypad enter as the regular enter for the
purposes of completing a text entry or activating the currently
selected link.
Add a little keyboard-related debugging.
Don't call select text to extend the selection if the tap
point hasn't moved.
A separate change to the Browser app adds more keyboard
accelerators.
bug:3270434
bug:3191699
Change-Id: I8a38b26196e93e344dc2a4b39a6968fe0c158d47
Context from an Activity are not meant to be store past the
lifetime of the Activity.
Fix for bug 3306898
Change-Id: Ib2f12cbdc3ec8aa0a6adf4770e6be4569fa6402c
Now checking if the ProxyProperties object is null, and if the
string returned by getHost() is null.
Change-Id: I727e26c2a41fe057501c3b610ba6fa221d16da45
We were leaking the first WebView created since we kept a reference
in a static variable. Using the new way of sending messages in a
static method to avoid this.
Change-Id: Ibb665e32c22c16c17176cd69bf8f7e83fd94894f
This class gives fairly low-level access to the HTTP cache, which
as far as we can tell was only exposed for the benefit of Gears.
BUG=3270236
Change-Id: Ibce10ecf8b524d3f472affa2a37fe4de15efd2ed
This is needed to construct a cachable CacheResult object.
Currently only WebViewWorker is able to do this, by updating
the fields directly.
Bug: 3270236
Change-Id: I50148697dcee4d329e1436a2ce4c15224cb5ae30
This reverts CL https://android-git.corp.google.com/g/84508
After lengthy discussion we have decided that disabling CacheManager
is too risky for third-party apps, and that enough functionality is
still available for it to be useful.
WebView.loadUrl() will not add pages to the cache, but it is still
possible to add them manually via CacheManager.saveCacheFile().
Change-Id: I6cfd9f93bb8d685450f048375adad9d17fa4eeba
