Chrome://Flags>Touch Event API is now disabled instead of automatic
Reported by
a...@footholdtechnology.com,
Nov 20
|
||||
Issue descriptionChrome Version : 70.0.3538.102 (Official Build) (64-bit) (cohort: Stable) URLs (if applicable) : demodb.footholdtechnology.com Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari: PASS/FAIL (N/A) Firefox: PASS/FAIL (N/A) Edge: PASS/FAIL (N/A) What steps will reproduce the problem? (1) Chrome://Flags (2) Touch Events API (3) Now disabled What is the expected result? I would expect it to be set to automatic, this is breaking things in our web based EHR like electronic signatures unless the flag is changed back. What happens instead? It's set to disabled, this was not discussed in any release and our customers are notifying us of the issue. Please provide any additional information below. Attach a screenshot if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Nov 21
,
Nov 21
Thanks for filing the issue! As per comment# 0 from the reporter, issue seems to be a Feature request, hence marking it as Untriaged. Thanks!
,
Nov 22
Please look at the duplicate issue for the temporary workarounds. But at the end you need to update your web app to use standards API and that flag deprecated the non standard API and there is no plan to expose it again. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Nov 20Components: Blink>Input