Issue metadata
Sign in to add a comment
|
Touch screen signature input using canvas is broken
Reported by
kacar...@gmail.com,
Nov 27
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Example URL: An internal application, not publicly accessible Steps to reproduce the problem: 1. Tap touch to enter a signature in an HTML5 canvas/JavaScript signature box. 2. Move your finger around to sign. What is the expected behavior? A signature appears in the box. What went wrong? No signature appears, although visual feedback shows that the movement is being tracked. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? Yes 67.0.3396.99 for sure but possibly later Does this work in other browsers? Yes Chrome version: 70.0.3538.110 Channel: stable OS Version: 8 and 10 Flash Version: This is for an internal application using this library: https://github.com/tomichj/signature-pad-rails The signature works on Android's version of Chrome as well as Firefox on the same Windows 8 and 10 versions where the signature is currently not working.
,
Nov 28
kacarter@ Thanks for the issue. Tested this issue on Windows 10 using HP EliteBook touchscreen laptop on the reported version 70.0.3538.110 and the latest Canary 72.0.3623.0 and unable to reproduce the issue by following the below steps. 1. Launched Chrome and opened a sample JSFiddle which has Touch screen signature input. 2. Signed with the finger in the signature box and can observe that the signature appeared. Attached is the screen cast for reference. Request you to check and confirm if anything is missed from our end in triaging the issue. Also request you to retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations. Thanks..
,
Nov 28
Hi, I guess something is missing because although that particular fiddle works on our machine, this one does not: https://jsfiddle.net/jdpe6obt/3/ The JavaScript is just copy/pasted from our application and contains only the JavaScript that comes from the library. We have been trying with a blank Chrome profile, no extensions or anything.
,
Nov 28
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 29
kacarter@ Thanks for the update. Able to reproduce this issue on Windows 10 and Ubuntu 17.10 on the reported version 70.0.3538.110 and the latest Canary 72.0.3625.0. Unable to confirm Mac OS behavior as Mac touchscreen laptop is not available at TE end. Unable to provide the bisect information as the issue is inconsistent. On Windows, could observe Good behavior on 65.0.3325.230 build, bad behavior on 66.0.3326.0 and again good behavior on 67.0.3396.99 build. On Linux, could observe bad behavior on 60.0.3112.0 build. Hence marking this issue as Untriaged for further updates from Dev. Thanks..
,
Nov 29
This is related to the recent deprecation of ontouch attribute listeners in Chrome. See https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/KV6kqDJpYiE I believe the issue with the library is here: https://github.com/tomichj/signature-pad-rails/blob/master/app/assets/javascripts/signature-pad/jquery.signaturepad.js#L448 This line needs to be updated to use addEventListener('touchstart', ...) rather than window.ontouchstart = ... In the interim, you can flip this flag to "enabled" chrome://flags/#touch-events to undo the recent change and get apps working again. However, this is a short-term fix that will eventually go away so the recommended path forward is to update code. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Nov 27