Merging to M59 seems very unlikely (does the severity of this deserve a post-mortem?). Where you able to reproduce on M60? Also this mostly ChromeOS only?

This issue is marked as a release blocker with no OS labels associated. Please add an appropriate OS label.

All release blocking issues should have OS labels associated to it, so that the issue can tracked and promptly verified, once it gets fixed.

Thanks for your time! To disable nags, add the Disable-Nags label.

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

I only repro'd on Chrome OS. I was not able to repro on Mac 59.0.3071.86 (stable).

@dpapad not sure if a post-mortem is necessary, but would certainly like to know why this wasn't fixed with  Issue 657718 .

Assigning this to @stevenjb for further investigation. I don't have a way to run ChromeOS ToT on a device with an actual touch screen, and can't seem to be able to simulate two finger scroll from DevTools' device mode.

Why is this marked ReleaseBlock-Stable, this seems like a minor regression?

It is extremely unlikely that I will be able to investigate this for 61, we would need to find another owner.

If the priority is lower go ahead and assign this back to me.

Summarizing action items per my understanding:
 - Find which commit fixed the issue (@tbuckley is not able to repro on Canary).
 - Figure out if issue still happens on M60.
 - If yes, attempt to merge fix to M60.

@dpapad and I confirmed it works as expected in 60.0.3112.34. Closing this bug since we won't merge a fix into M59 stable.

Apparently, the fix for  issue 657718  was briefly reverted ( issue 697751 ) so that probably explains the version gap.