| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Delete all the Java classes used only by the old WebView implementation,
and also sections of common classes that were only needed for the old
WebView.
Bug: 10427705
Change-Id: I02549a71104b35d86d99058c71f43e054730ec7d
|
| |
|
|
|
|
| |
Bug: 6554060
Change-Id: Iad263c78a0e1504dd10e9ef5b92505bca6991cbc
|
| |
|
|
|
|
| |
Bug: 6317798
Change-Id: Ia1652e9030e877e270326e9e8a8b040810b89f09
|
| |
|
|
|
|
| |
Bug: 6490959
Change-Id: I5a6cfa3d36f1df28d9c3b03e120f59581ee22c01
|
| |
|
|
|
|
|
|
| |
Bug: 6490959
Fixes the issue where we will show the old tap highlight
if webkit isn't quick enough to respond
Change-Id: Icd9864d276b6ad311e3f3dc4deaa7085e3769006
|
| |
|
|
|
|
| |
Bug: 6490959
Change-Id: I0f447f65c84f9ce208ce52caba05e7dcb2f76bc5
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
Bug 6410164
Change-Id: Ia3907a9a57321d0f25763c88fd0c0a7617d5da48
|
| |
|
|
|
|
| |
oops
Change-Id: I667b849af4c5d4fece42e9bcbc5b6b9951b955bb
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
Bug: 6319429
Change-Id: I8eb989d94433c01406cdb32e01034c644078a133
|
|
|
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
|