New issue
Advanced search Search tips

Issue 896652 link

Starred by 1 user
Status: Duplicate
Merged: issue 897906
Owner: ----
Closed: Oct 23
Cc:
nzolghadr@chromium.org
eirage@chromium.org
bokan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Signature.js not working correctly

Reported by jason.wi...@unipartdorman.co.uk, Oct 18 
UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36

Steps to reproduce the problem:
1. Log on to http://keith-wood.name/signature.html
2. Try and complete "Default Signature" on touch screen

What is the expected behavior?
Create free-hand signature using signature.js and touchscreen

What went wrong?
Unable to draw using touchscreen

Did this work before? Yes 

Chrome version: 70.0.3538.67  Channel: stable
OS Version: 10.0
Flash Version: 

http://keith-wood.name/signature.html <- JS plug in installed on local intranet site.

Comment 1 by dtapu...@chromium.org, Oct 18

Cc: nzolghadr@chromium.org
Components: -Blink Blink>Input

Comment 2 by nzolghadr@chromium.org, Oct 18 

I just tested this with 69.0.3497.100 on Windows and it didn't work with that either. I also tested with Edge and I don't seem to be able draw anything with my finger on the canvas. Do you have this working anywhere?

Comment 3 by jason.wi...@unipartdorman.co.uk, Oct 19 

It was working perfectly on Chrome < v70, I have been using it for 3 years now on a local intranet site being used daily.

Comment 4 by bokan@chromium.org, Oct 19

Labels: OS-Linux
This does work in Firefox on Linux. The element has mouse event handlers but nothing for touch. I'm guessing there's a difference in the mouse event emulation.

I tried as far back as M66 and it didn't work for me either though so I'm also not sure this is a recent regression. jason.williams@, is it possible you had something set in chrome://flags ?

Comment 5 by bokan@chromium.org, Oct 19

Cc: bokan@chromium.org
Status: Untriaged (was: Unconfirmed)

Comment 6 by bokan@chromium.org, Oct 19

Cc: eirage@chromium.org
I wonder if this has to do with making the ontouch APIs disabled by default: https://www.chromestatus.com/feature/4764225348042752

That happened in M70. OTOH, flipping the flag in chrome://flags to enabled doesn't help. +eirage@

Comment 7 by chris.st...@sansio.com, Oct 23 

I had found for our devices it is because the touch api is disabled by default since M70

Comment 8 by eirage@chromium.org, Oct 23

Status: WontFix (was: Untriaged)
(note that only ontouch* are disabled, but touchs are still function, you can still use touch events via addEventListener)

Comment 9 by bokan@chromium.org, Nov 29

Mergedinto: 871829
Status: Duplicate (was: WontFix)

Comment 10 by bokan@chromium.org, Nov 29

Mergedinto: -871829 897906
►

Sign in to add a comment