Issue metadata
Sign in to add a comment
|
After using a 3rd party script (Signature via HTML canvas) <option> of the <select> tag is not clickable any more in Windows 10
Reported by
mark.hub...@gmail.com,
Apr 28 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. Use a Win10 touch device 2. go to this page https://willowsystems.github.io/jSignature/#/demo/ or this jsfiddle: https://jsfiddle.net/8qhzz93c/2/ 3. Use the signature field with touch (!) not mouse and then after try to select a different option in from the select tag What is the expected behavior? By selecting a different option, this option should become selected What went wrong? selected option does not become selected Did this work before? N/A Chrome version: 57.0.2987.133 Channel: stable OS Version: Windows 10 Flash Version: Issue does not appear in the latest version of Chrome Canary. It also only appears in combination with this 3rd party script and also only on a touch enabled Win10 device (not with the mouse). I was wondering, just out of curiosity (if you are not too busy), what caused this?. Thanks in advance, Best!
,
Apr 28 2017
Hi, Thanks for the quick reply, I realized I used an outdated version: 57.0.2987.110 However, when I click the settings button, I don't see an opportunity to update as explained here: https://support.google.com/chrome/answer/95414?co=GENIE.Platform%3DDesktop&hl=en-GB Thanks again for taking the time, Best, MArk
,
Apr 28 2017
Thank you for providing more feedback. Adding requester "rbyers@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 29 2017
It's possible that the update is still rolling out. You can try to provoke it by going to chrome://chrome. What about the incognito window? Some extension causing a problem here is my best guess so far.
,
May 1 2017
,
May 1 2017
Sorry, forgot to reply, I deleted all extensions, uninstalled chrome, reinstalled it, didn't log in any account, tried it in incognito mode, however, issue is still there.
,
May 1 2017
Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 4 2017
I tried on a Dell laptop on Windows 10 and it appears to be working fine as well. I tried both examples you provided. Do any errors appear in devtools? Did you have any luck with Chrome 58?
,
May 4 2017
Hi, Thanks for taking the time! Unfortunately, nothing reported in the dev tools/console, it works fine in Chrome 58, the one I was using was Chrome 57.0.2987.110 I was just curious what it was, not that important I guess. Thanks again, Mark
,
May 4 2017
Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 4 2017
So this an issue now that you M58 is rolled out to stable now right? All is good?
,
May 4 2017
Yes, as I mentioned before, it is stable in the current version. I was just wondering if there's a way to find out why it didn't work with the previous version, just out of curiosity. Thanks again, Mark
,
May 4 2017
Closing issue no longer reproducible. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rbyers@chromium.org
, Apr 28 2017Labels: Needs-Feedback
NextAction: 2017-05-07