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
Multiple paths were redundant, as they both synchronized the layers, and drew
the base if needed.
Depends on external/webkit change: https://android-git.corp.google.com/g/#/c/179965/
Change-Id: I1c355510f6edda4631190f2d26df8171e795a6ac
We now allow processes that currently have stopping activities to
be managed as if they were done stopping, so that memory trimming
can be done before the process goes to the background. Hopefully
this will reduce cases where the processes goes to the background
and immediately gets killed, but wouldn't have had to be killed if
it had a chance to trim its memory.
Also change window memory trimming to always do the aggressive
trimming when memory is critical, even if not on a low-end device.
And tweak web view trimming to not trim for foreground UI events.
Change-Id: I241b3152b52d09757bd14a202477cf69c9b78786
This was deprecated and the replacement provided in API level 3.
Hiding it in API 16 as a step toward removing support for it in 17.
Bug: 5012841
Change-Id: Ice66a0fc1031c0d6705973dae7cbc11b028e14c9
Bug: 5032345
During the zoom, the embedded titlebar doesn't get rendered
in the correct spot. Browser renders the titlebar differently
now, so the old code can be removed
Change-Id: I6affc9e6119dc17e89d15dad77e14e1cdf139662
Several of these are duplicated; referring to a single source makes the code
paths using them easier to track down.
(also removing a spurious import)
Bug: 6237833
Change-Id: Ibdacc124c047e37c7f0ced9ecc6f26ae3e6b4326
Bug: 6142700
WebKit is sending an empty inval rect for some reason, which results
in WebView not being invalidated. Assume an empty inval means a
full inval
Change-Id: Ib93b806f8f8fd2039e2a0e43de2372c3e6be2433
