Able to reproduce the issue on Windows 10 and Ubuntu 17.10 using chrome reported version #70.0.3538.67 and latest canary #72.0.3588.0.
Note: Could not check the issue on OS-mac as test team doesn't have a touch screen mac to test the issue.

Bisect Information:
=====================
Good build: 69.0.3497.128
Bad Build : 70.0.3498.0

Change Log URL: (From omahaproxy)
https://chromium.googlesource.com/chromium/src/+log/69.0.3497.0..70.0.3498.0?pretty=fuller&n=10000

From the above change log suspecting below change
Change-Id: I97f785a8bc0534cf7f23e33d65550921627789db
Reviewed-on: https://chromium-review.googlesource.com/1143592

nzolghadr@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.
Note: Adding stable blocker for M-70 as it seems to be a recent regression. Please feel free to remove the same if not appropriate.

Thanks...!!

krajshree@ that CL doesn't seem to have changed what the reporter says.

repoter, can you elaborate a little more on what flag you are talking about. In chrome flags are you referring to "#touch-events" (i.e. Touch Events API) flag?

Ella, I believe this is related to your change. Did you intend to have it reach the beta/stable for M70 because I see the revert in M69?
https://chromium-review.googlesource.com/c/chromium/src/+/1150702

Yes, this is intended.  
See: https://www.chromestatus.com/feature/4764225348042752

(note that we only disabled ontouch*, but touchs are still function, you can still use touch events via addEventListener)

 Issue 898045  has been merged into this issue.

Our company has been using roughly 50 Asus touchscreen Chromebooks to capture signatures in our Electronic Health Record.  They have worked flawlessly until the OS 70 update.  By turning the Touch Events API back to Automatic, it works as expected again.

We found that as well, but are worried that the next release will flip the
"Touch Enable API" flag again, by changing the code from

this.ontouchstart = func...

to

this.addEventListner('touchstart',...


It works with the "touch enabled API" flag disabled and I don't believe an
update will break us again.

Can an update be applied that sets the condition to Automatic? This (along with a forced enabled setting) fixed our problem in the education sector. 

Thanks everyone for your understanding. But playing with the flag is not the right way to fix the problem. At some point in the future that flag will be removed altogether and you wouldn't be able to just change the value of that flag anymore. As Shannon also mentioned changing the code to use the standard approach should be the solution.

I'd like to also encourage you to communicate the issue back to the framework/library owners in case you are using one so hopefully this gets fixed for more people if they fixed the issues in their library.

I can appreciate that the better solution is changing the code, but if we do not have access to the code, what are we supposed to do?

 Issue 907122  has been merged into this issue.

 Issue 904233  has been merged into this issue.

 Issue 908397  has been merged into this issue.

 Issue 908873  has been merged into this issue.

 Issue 903461  has been merged into this issue.

 Issue 896652  has been merged into this issue.