Gmail use WebView without instantiating the gesture detector. The Gmail team replied that they don't need the pinch to zoom feature so we can safely skip multi-touch events for them.
Change-Id: Id60a4d4583979ef5b420fff04c4ca097c0594024
Cherry picked:
Add an api to toggle content url access.
By default, WebView allows access to content providers on the system. This
setting allows applications to turn off content urls.
Bug: 1196879
Change-Id: I49eaea6d7b9ccc3b3a4443d712222556087568c0
bug:3341772
1. Now a key in the binding is represented as a long with 32 MSB for modifiers and 32 LSB for keyCode.
bug: 3340732
1. Added check in the WebView key handling code to diable the accessibility injector/injected script in
case accessibility is been disabled after loading the content.
Change-Id: Ic3746dff16ec77ba682a5b139cec0e6afd8fc839
Bug:3313519
In Find ActionMode, Enter should call find on page (rather than
advancing focus to the WebView).
In TextView, pass and Enter key down to super, so that the
pressed state can get called properly, and the
onClickListener will fire.
Change-Id: Ia875fa6b5cf02565a0d066a009e68ce97718b032
The feature was enabled to prevent flash sites from flickering due to
viewport height change when the site is scrolled.
Now fixed viewport height is in honeycomb, this flickering shall be
a non-issue. So to support better scrolling of overflow:hidden sites
and better consistency, overflow:hidden in overview mode is ignored
as well.
Tested on flash site http://home.disney.go.com/mwc.index to make sure
no flickering happens. More testing shall be done once good flash
player is there.
issue: 3330038
Change-Id: Ia3f61ce49cfb970d26976d4e876c337d210a9df2
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
