-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select/option doesn't work in chrome 53 for touch events #8181
Comments
Thanks, taking a look and seeing about getting a fix here ASAP |
Alright here are my findings so far on this issue:
|
I created a local file
And it doesn't open the select in Chrome DevTools (any mobile mode). It is a bug out of ionic scope, ref SO link and Chromium link. |
Hi, I did the same kind of test as @WashingtonGuedes . The select tag was working alone. But as soon as I enabled the ionic library, the bug appeared again. So there was an issue in the ionic scope, although there is still a bug with select in chrome dev mode with the dropdown opening completly out of the page, but that's another story. Thank you guys |
This is not a bug in Chrome - it is a security feature. I have seen this warning in Chrome DevTools for a few weeks (didn't have time to investigate it) but I was using Ionic 1.2.4 - I updated last week to Ionic to 1.3.x and it was still there. I found that this warning always appeared when I clicked on the option select:
I tracked this to this function in ionic.bundle.js (line ~2950) which is dispatching a click event... Which is exactly what the Chrome Status page says should not be happening (from JavaScript).
Now I have updated to M53, I don't see this warning... and I can't open any select controls on my app in Chrome nor on my Samsung (Android 6.0.1). I presume users of my in-production app will not be able to use the drop downs until it is fixed either... I will try the fixes from @jgw96 ... EDIT: No luck with data-tap-disabled in Chrome. The trouble is, in the calling function tapClick(e) (~line 2932 ionic.bundle.js), e is trusted.
But the clickEvent generated by document.createEvent("MouseEvents") in the triggerMouseEvents() function is untrusted... and initMouseEvent is deprecated. Microsoft's page about createEvent says that the event created will always be untrusted for security reasons... clickEvent = MouseEvent {isTrusted: false, |
Here it is the issue on googles chrome forum |
I was thinking perhaps to replace my SELECT with a button that opens a modal list and then return the value I want from the selected item in the list... something like this: |
I have now switched my select control to an ionic-Select-Control and it works well - it uses a modal window instead of a select control.... |
What about something like this;
then you just add ;
|
Just pushed a fix for this that will work regardless of the UA setting. Will try to get a release out in short order |
Thanks @mlynch @dennybiasiolli. Issue is fixed in version 1.3.2. https://github.com/driftyco/ionic/releases/tag/v1.3.2 |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Short description of the problem:
Select/option doesn't work in chrome 53 for touch inputs. (Through chrome dev tools and native devices.)
What behavior are you expecting?
Select element should work without any issues in chrome 53+ for touch events.
Steps to reproduce:
Other information:
data-tap-disabled = "true"
for parent element, but issue's still there.Which Ionic Version? 1.x or 2.x
Provided pen has
1.3.1
. I use1.1.0
Plunker that shows an example of your issue
http://plnkr.co/edit/TJSmtfyOrLUNJWmjsADN?p=preview
The text was updated successfully, but these errors were encountered: