This repository was archived by the owner on Jun 9, 2022. It is now read-only.
Fastclick breaks <select> on Chrome 53+ #497
Comments
RByers
changed the title
elie222
added a commit
to elie222/meteor
that referenced
this issue
Dec 30, 2016
See here: ftlabs/fastclick#497 And here: https://productforums.google.com/forum/#!topic/chrome/Q4Rt6d0C4Qo I just spent hours trying to figure out why selects haven't been working on my site, and finally found out it was fastclick.
|
Got bitten by this today. The Browserstack fleet of devices must've just received updates past Chrome 53 because I'm suddenly seeing this issue go all the way back to Android 4.4 now. In newer projects I stopped using Fastclick because of wider support of better touch handling, but looks like I need to start pulling it out of older projects. Heading that direction now. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We (chromium) fixed our spec-compliance bug that allowed JS-generated
mousedownevents to open<select>boxes in Chrome 53. We just realized now (as 53 is going out to Android stable) that this breaks fastlick. Of course there's no good reason to rely on FastClick on Chrome anymore, but lots of pages still do.We're still trying to figure out if we should undo our chromium change. But separately, perhaps FastClick should stop relying on this non-standard behavior? Maybe instead just don't intercept touches that go to
<select>boxes?Even better, just do #498.
The text was updated successfully, but these errors were encountered: