To try to extract some more data about the circumstances, you can try 2
things:
1. scan the app logs for error or debug messages about touch events: is
there anything suspicious in the logs when that error occurs ?
2. start an app that is prone to exposing the issue with the --inspector
flag; the easiest way is to go modify the desktop file in /opt/click and
add the flag on the app commandline. Then, once the issue occurs, connect
on the debug console from Chrome (http://<ip of your phone>:9221) and watch
the JS console
On Tue, Sep 15, 2015 at 2:59 PM, Alexandre Abreu <
<email address hidden>> wrote:
To try to extract some more data about the circumstances, you can try 2
things:
1. scan the app logs for error or debug messages about touch events: is
there anything suspicious in the logs when that error occurs ?
2. start an app that is prone to exposing the issue with the --inspector
flag; the easiest way is to go modify the desktop file in /opt/click and
add the flag on the app commandline. Then, once the issue occurs, connect
on the debug console from Chrome (http://<ip of your phone>:9221) and watch
the JS console
On Tue, Sep 15, 2015 at 2:59 PM, Alexandre Abreu <
<email address hidden>> wrote:
> I haven't been able to repro it yet on Mx4, /bugs.launchpad .net/bugs/ 1494770 /bugs.launchpad .net/canonical- devices- system- image/+ bug/1494770/ +subscriptions
>
> --
> You received this bug notification because you are a bug assignee.
> https:/
>
> Title:
> Scrolling inertia for webapps died on Meizu MX4 (stable channel)
>
> To manage notifications about this bug go to:
>
> https:/
>