Skip to content
This repository has been archived by the owner on Dec 7, 2021. It is now read-only.

Fallback to native interface on mobile devices #14

Open
jonnyscholes opened this issue May 2, 2017 · 5 comments
Open

Fallback to native interface on mobile devices #14

jonnyscholes opened this issue May 2, 2017 · 5 comments

Comments

@jonnyscholes
Copy link

It would be awesome if on mobile devices when interacting with the select it could use the native interface provided by the OS. Perhaps as an option so that if some people wanted to keep the search functionality etc around, they could.

Thanks for the great lib!

@Mobius1
Copy link
Owner

Mobius1 commented May 4, 2017

I'll add this to a future release. Great idea 👍

@Mobius1
Copy link
Owner

Mobius1 commented Jun 15, 2017

This has now been implemented. I've tested it on Android, iPhone and Kindle (HDX) and it works. However it's a little glitchy and sometimes it takes a couple of taps to get the native box to appear. I'll continue working on it to improve it for future releases.

@Mobius1 Mobius1 reopened this Jun 17, 2017
@JPustkuchen
Copy link

Great idea. I think responsiveness is very important to provide a modern (multi)select solution. Perhaps it should be configurable which interface to use on which mobile devices?

@jenstornell
Copy link

This issue will be more and more important I think, because most people use mobile devices these days. It will be even more in the future.

@hashimaziz1
Copy link

hashimaziz1 commented Sep 11, 2020

I understand this framework isn't in active development but did this ever get implemented? I'm currently having trouble with an older version baked into a Wordpress plugin - on mobile the dropdown is only clickable by selecting the text, anything outside of it doesn't trigger. Is this a known issue or was it ever fixed?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants