2dc3ffd31a9cf445817e868db6dee14569623c08 |
|
30-May-2012 |
John Reck <jreck@google.com> |
Don't long press if preventDefault is called Bug: 6554060 Change-Id: Iad263c78a0e1504dd10e9ef5b92505bca6991cbc
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
c1e80a360a43ea52092dda79138c9d55a5588fc0 |
|
25-May-2012 |
John Reck <jreck@google.com> |
Support skipping a touch stream due to lack of handlers Bug: 6317798 Change-Id: Ia1652e9030e877e270326e9e8a8b040810b89f09
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
aa5af8d004a0846cf111c954cfcdf799157f16d6 |
|
18-May-2012 |
John Reck <jreck@google.com> |
Don't show the touch highlight for double taps Bug: 6490959 Change-Id: I5a6cfa3d36f1df28d9c3b03e120f59581ee22c01
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
eb11f47353102deb13c73b9c1106ed34761cd784 |
|
17-May-2012 |
John Reck <jreck@google.com> |
Tweak show/hide of touch highlight Bug: 6490959 Fixes the issue where we will show the old tap highlight if webkit isn't quick enough to respond Change-Id: Icd9864d276b6ad311e3f3dc4deaa7085e3769006
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
94c478e9e59683fd552fd11b2b7b27fac78b90b4 |
|
17-May-2012 |
John Reck <jreck@google.com> |
Don't send an ontouchmove until slop is exceeded Bug: 6490959 Change-Id: I0f447f65c84f9ce208ce52caba05e7dcb2f76bc5
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
41f73bdf4d915305152ba2053b7523bf5f90ffa8 |
|
15-May-2012 |
John Reck <jreck@google.com> |
Always do a HIT_TEST Bug: 6490959 The issue here is that if the page calls preventDefault on a touchstart handler WebViewClassic will not do a HIT_TEST as it doesn't get the ACTION_DOWN. This means that the mouse is in the wrong position when the click ultimately fires. This changes it so that WebViewInputDispatcher will always do a HIT_TEST at the start of a touch stream, which ensures that the mouse is positioned correctly. Change-Id: I1aaca7692e2c7aeedeb21fa3592cd4cb3223ea25
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
387c2e8d425651475c674018951a4047bf4f3cb4 |
|
11-May-2012 |
John Reck <jreck@google.com> |
Prevent updateStateTrackers from being affected by preventDefault() Bug: 6477996 Calling e.preventDefault() on a javascript touch handler is apparantly not supposed to prevent the default gesture detector, who knew? Change-Id: I6ee36e2fbc485b289b6dbb3464d8562c88e3be49
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
84fa241f6c6f8b9f72371dd540515ba8041dd6b7 |
|
04-May-2012 |
John Reck <jreck@google.com> |
Fix tap highlight annoyingness Bug: 6108346 Highlight now correctly doesn't show up unless it is a click, and no longer has any weirdness with sticking around unusually long Change-Id: I06f6eae45d970085232466f17cbbd9ebaefc4d69
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
7a33acf123ad27aad21bd517fca68a64eb8fe434 |
|
03-May-2012 |
George Mount <mount@google.com> |
Add intercept path for UI touch handling. Bug 6410164 Change-Id: Ia3907a9a57321d0f25763c88fd0c0a7617d5da48
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
d7156d3f471976490bdc7c76f714aedbfa3e1682 |
|
24-Apr-2012 |
John Reck <jreck@google.com> |
Use the right timeout oops Change-Id: I667b849af4c5d4fece42e9bcbc5b6b9951b955bb
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
3f1679cba0fc33ef8054d89e41d6716d0a260f9b |
|
13-Apr-2012 |
John Reck <jreck@google.com> |
Remove an unnecessary sanity check This is causing issues with MotionEvents built by various tools such as DRT. The check itself doesn't seem strictly necessary, and it is easier to remove the check than fix all the tools and tests Change-Id: I74bf85307956b5858042fbe23f87ed2b87132f17
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
2d8c13bd1cf17842747b5e293e940169a26fa0d2 |
|
12-Apr-2012 |
John Reck <jreck@google.com> |
Improve when highlight rects are shown Bug: 6319429 Change-Id: I8eb989d94433c01406cdb32e01034c644078a133
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|
9d3bdbd6b8f9eda5f67212b06185cd59adcda6c8 |
|
21-Mar-2012 |
Jeff Brown <jeffbrown@google.com> |
New WebView input dispatcher. Bug: 6317798 Stuff that's better: 1. We maintain two queues in a way that ensures that WebView and WebKit both see consistent streams of events, even in cases where WebKit times out. We send ACTION_CANCEL if necessary, etc. 2. All pointer events go through the same channel, including hover and click ("touch up") events, to ensure correct ordering. 3. Given that the input events are in a separate queue, we can force execution of all of these events whenever we like, making new latency optimizations possible. 4. The entire history of each touch event is sent to the web application to enable smoother interaction. 5. The web application may choose to intercept a touch event stream at any time by issuing "prevent default". Previously, it could only prevent default on the initial down event. The new behavior is more standards compliant. Change-Id: I42d2d045e7d44af7c54b29570f188b7400d91d4e
/frameworks/base/core/java/android/webkit/WebViewInputDispatcher.java
|