Bumping to P1. Probably deserves release-block;)

Patch is at https://chromium-review.googlesource.com/582429

Note that the failure only happens on Win8+, and only happens after you use a stylus (touching the screen about 32 times).

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1f6bcbedab3fc3918c7467c135a4f6bd2d4bf70d

commit 1f6bcbedab3fc3918c7467c135a4f6bd2d4bf70d
Author: Eugene Girard <girard@chromium.org>
Date: Tue Jul 25 19:24:51 2017

Map pointer events, touch events so event-id's are small.

Bug:  747642 
Change-Id: I132ba496a68121bf09a3826d456b75fab43401cb
Reviewed-on: https://chromium-review.googlesource.com/582429
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Eugene Girard <girard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#489398}
[modify] https://crrev.com/1f6bcbedab3fc3918c7467c135a4f6bd2d4bf70d/ui/views/win/hwnd_message_handler.cc

Confirmed the fix in today's canary.

This bug requires manual review: Request affecting a post-stable build
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), ketakid@(ChromeOS), govind@(Desktop)

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

I number of reports are coming in that touch pad fling is broken in Chrome 61 stable. This appears more widespread than comment #3 indicates.

I've confirmed building m61 branch with this patch fixes the touch fling issue on Windows 10.

Merge approval is pending based on internal mail thread "Re: Late patch for M61", waiting on girard@ & dtapuska@ confirmation on how safe is the merge.

I can confirm the bug on 2 Surface Pro 4 devices since Release-61 (61.0.3163.79). Current beta does not fix the bug but the fix in current Canary seems to work. I hope the patch gets merged asap - the bug has killed my workflow.

This issue is fixed by commit e976a3897d7a8abbbacce4c2622cc5ecf5a7b067 which is under merge review in  issue 762386 

This  is NOT fixed. I still have the same problem on Tuesday 12 Sep 2017

Same here, inertial scrolling not working, tested on Lenovo Miix2 8 (windows 10) and W10i (oem win tablet win8.1) all 32bit version windows. Canary works OK.

The issue is fixed, they are just deciding if it gets merged back to 61.  I'm using Canary and the issue is fixed there and you can run that side by side with an existing 61 installation.

It has been merged back to 61. It is just when a new 61 build is deployed. 

Sorry but for me it is not fixed. Once 61 is updated then u can say it is fixed. 

This is not fixed. Been having this problem and it still very much a problem as of today

It worked for only a few seconds and then stopped. I disabled all extensions,
but no change.

If you want to report a broken or fixed verdict, please indicate which version of chrome you're using - you can find it in chrome://version.

If you're testing on 61.0.3163.79, then you should expect this to be broken. The fixed version is still under evaluation and will hopefully roll out soon.

Sorry for all the hassle, and thanks for helping us out on this issue - bug reports and feedback are important to us.

I am using Version 61.0.3163.79 (Official Build) (64-bit).
I am not a tester. This is the version that was uploaded
onto my computer.

This is not fixed on Chrome version 61.0.3163.91

This is not fixed on Canary version 63.0.3215.0

I should add - I am using Windows 7.  No touch screen - however websites that employ 'mousewheel fling' (i.e. use the mouse wheel to mimic touch fling) are still broken for me as they have been for the past week or so.  

I'm on Windows 10 and touch screen scrolling (and the inability to use
touch for the upper right corner buttons) is fixed in both 61.0.3163.91 and
63.0.3215.0.  It may be a different issue that you have.

Well, I came across multiple complaints in the help forums and they all linked here.  I suspect that the problem was wider than Google has acknowledged and that it is merely partially fixed at the moment. 

Everything now works.