Select element stops working with touch only
Reported by
joel.l...@pearson.com,
Mar 13 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Go here: http://test89-tn8.pearsondev.com/client/index.html?username=LGN000225484&password=T83YA62F 2. Press the Start Test arrow 3. Go to user dropdown in top right and select "Change the background and foreground color" 4. Select any color and close the menu 5. Now try to select a choice in one of the select elements using touch What is the expected behavior? You should still be able to select an option using touch What went wrong? After opening another menu, the select element can no longer be used using touch Did this work before? N/A Does this work in other browsers? Yes Chrome version: 57.0.2987.98 Channel: n/a OS Version: 10 Flash Version: Shockwave Flash 24.0 r0 This is related to this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=623876. In version <=56 repeating these steps causes a click to be triggered an a different element, but in 57+ the select element becomes unusable with touch (mouse can still select a choice normally) Reproduced on Windows 10 touch and Chromebook touch (Chrome 57+)
,
Mar 14 2017
,
Mar 14 2017
nzolghadr@ please investigate. I can reproduce something strange in that I can open the select box every time after changing the color via touch but not every selection allows me to select something. After about 3 attempts at opening the select box then I can start changing the items.
,
Apr 7 2017
nzolghadr, could you take a look at this bug or reassign to someone?
,
Apr 7 2017
I tested this and I couldn't reproduce it. I tested both on Windows 10 and Android. I also talked to Dave and he doesn't seem to be able to reproduce the bug either. Joel, can you see whether you can see the bug happening in the latest version and let us know what you do again? A screen capture of what you do and the bug would be very helpful.
,
Apr 7 2017
It looks like this issue is fixed as of Chrome 59.
,
Apr 7 2017
Good to hear that. Let us know if it comes up again. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by joel.l...@pearson.com
, Mar 13 2017