You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
While giving the frontend Webcomponent (lit-signature-pad) a bigger overhaul I tried to update the npm package (signature_pad) to 4.0.1
I changed to code to use the new EventEmitter methods that were mentioned in the changelog. But the "endStroke" Event (mousebutton was released to stop painting), which is used to send the image uri to the Java Backend was never emitted, where "beginStroke" (mousebutton is clicked and hold to start painting) was always send correctly.
Need to investigate a bit more, but still wanted to make a minor release.
To Reproduce
Steps to reproduce the behavior:
Update signature_pad to 4.0.1
Refactor code to use EventEmittor (.addEventListener)
"endStroke" is never sent
Expected behavior
"endStroke" Event should be sent
Edit:
Signature_Pad 4.0.2 has been released, so I have to test it with the new version.
The text was updated successfully, but these errors were encountered:
F0rce
changed the title
Investigate signature_pad 4.0.1 not working in a webcomponent environment
Investigate signature_pad 4.0.2 not working in a webcomponent environment
Jan 25, 2022
Describe the bug
While giving the frontend Webcomponent (lit-signature-pad) a bigger overhaul I tried to update the npm package (signature_pad) to 4.0.1
I changed to code to use the new EventEmitter methods that were mentioned in the changelog. But the "endStroke" Event (mousebutton was released to stop painting), which is used to send the image uri to the Java Backend was never emitted, where "beginStroke" (mousebutton is clicked and hold to start painting) was always send correctly.
Need to investigate a bit more, but still wanted to make a minor release.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
"endStroke" Event should be sent
Edit:
Signature_Pad 4.0.2 has been released, so I have to test it with the new version.
The text was updated successfully, but these errors were encountered: