should read "fast wiping" (not "fast swiping") ;)

Hm, something went wrong, it should be component: Mobile>WebView

Uninstalling chrome and updating the android webview component to 61.0.3163.98  shows the same faulty behaviour in apps using webview.

Can you provide web site(s) you visited for this issue?

Thanks.

The problem can be reproduced on any website (which is large enough to scroll down).

I.e. https://mobile.nytimes.com

It does not matter if the page has images or not. Scrolling lags/stops on pages with text only, too.

The regression has been introduced between 60.0.3112.116 and 61.0.3163.98.

Just downgraded to 60.0.3112.116 and all is fine in chrome and my newsreader app which uses WebView to display the content.

I asked other users of the bq Aquaris X-Series and they could confirm this bug. I don't know if other devices from different brands are effected too but I think so.

Thank you for providing more feedback. Adding requester "ramine@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I've tried on a Nexus 5X and I don't see an issue on the nytimes page. I don't have a bq Aquaris X-Series device are you able to provide a video displaying the broken behavior?

Likewise a trace might be helpful from the device as well.

Confirmed. The Nexus 5x from a friend does not show this issue. It seems to be device specific.
The attached screen recording shows the lagging when swiping through the web site (repeated swipe with one finger). I will attach a second recording with WebView/Chrome version 60.0.3112.116. 

Deleted: 20171005_211859_edited.mp4 9.2 MB

	20171005_211859_edited.mp4 9.2 MB View Download

Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Swiping/scrolling with Chome 60.0.3112.116.

Deleted: 20171005_213354_edited.mp4 6.8 MB

	20171005_213354_edited.mp4 6.8 MB View Download

yfriedman@, aelias@ any chance you might have such a bq device?

nope, we have a really limited device library here, mtv has the most

Regressed between 60 and 61, so requesting exact bisect from manual test team to find the culprit change.

Not sure but this could be related, may be the same bug on a different device (WileyFox Swift 2X):

https://productforums.google.com/forum/#!topic/chrome/bB7Hwu4_Tzc;context-place=topicsearchin/chrome/android$20scrolling

I do not want to push but are there any news?

Can you provide link to the web site where scrolling is slow?

Thanks.

I already provided an example above. As I said, this problem exists an any web site, it is not related to any specific web site.

The scrolling is not slow in general, it hangs if I try to scroll fast with multiple touches/swipes down or up a site.

May be my two videos are not clear enough, but you can see, that version 60 scrolls really smooth without lagging/stopping.
In version 61 (and above, tried latest builds) it randomly lags/stops when it should not.

Even on web sites with text only (no images, no java script) are affected, e.g. the rfcs on https://tools.ietf.org/html/

Chrome: 61.0.3202.98
Test link: https://tools.ietf.org/html/

Result: Scrolling seems to be smooth w/ no apparent lagging with multiple scrolling, swipes.
Similar device tested on;  Xiaomi Redmi Note 4 and Motorola Moto G5 Plus.

Yes, it looks like only the bq aquaris x is affected. Maybe the Wileyfox mentioned above, too.

What could be the cause? Any ideas?

This is a really annoying bug.

I did two traces with chrome 60 and chrome 61. It looks like there is a problem with InputLatency::GestureFlingStart/Cancel.


I'll attache the version 61 trace in a separate comment.

Deleted: trace_chrome60_input_blink.json 8.4 MB

trace_chrome60_input_blink.json 8.4 MB View Download

Trace of chrome 61, scrolling through the same web site in the exact same manner.

Here you can see missing events of InputLatency::GestureFlingStart/Cancel.

Deleted: trace_chrome61_input_blink.json 8.2 MB

trace_chrome61_input_blink.json 8.2 MB View Download

Looks like recent Chrome beta 63 behaves correct. But other apps relying on WebView are still broken, even when selecting "WebView Chrome Beta" in developer options.

Would be nice to get some update information, e.g. was it a bug in chrome or is it a bug in the firmware of the BQ Aquaris X/XPro and Chrome 63 now incorporates a workaround which circumvents this bug?

paranoidandroid4284@ could you please confirm if the issue is fixed on apps using WebView or not?

paranoidandroid4284@ still awaiting a response from you.

paranoidan...@ I close this issue for now as I assume things are fixed not both in webview and Chrome latest version. Feel free to comment here or file a new bug if you still see the issue and we'll look into it again.