closeMenuOnSelect=false doesn't work on mobile chrome

[gafemoyano]

Are you reporting a bug or runtime error?

Bug
https://codesandbox.io/s/z6xlovo34?module=/example.js

I'm not sure if this is intended or not, but the menu doesn't stay open when I use it on my mobile phone.
Android, Chrome mobile.

Thank you for this great component, let me know what I can do to help.

[jbccollins]

I suspect the fix for this will be similar to the fix for #2577

69abb3f

[Tecktron]

I tested out the 2.0.0-beta.7 tag and this is still broken in Chrome on touch screen devices (Apple, Android & MS surface).

[Tecktron]

After some playing around, I found that setting blurInputOnSelect={false} fixed this issue for me. Hope that helps you as well.

[cptiwari20]

After some playing around, I found that setting blurInputOnSelect={false} fixed this issue for me. Hope that helps you as well.

This helps me. I am using [email protected]^. I had an issue in mobile multi-select drop-down. Every time I use to select one item it closes. But in desktop it was working properly. Now after using this method. It is working fantastic.

[kulttuuri]

FYI; If anyone is looking for solution to this, this is still broken in 3.0.8. Adding blurInputOnSelect={false} fixed this for me. Thank you!

[bladey]

Hi all,

Thank you everyone who had a part in addressing this question.

In an effort to sustain the react-select project going forward, we're closing issues that appear to have been resolved via community comments.

However, if you feel this issue is still relevant and you'd like us to review it, or have any suggestions regarding this going forward - please leave a comment and we'll do our best to get back to you!

[RebootGG]

It would be nice to address this even though the workaround by @Tecktron works just fine. I've spent a bit of time searching as why it didn't work on mobile, before I came accross this issue. There are also probably some people who didn't even test it and just assumed it worked on mobile, and are still not aware of the bug.

If this can't be implemented, we could at least update the docs with this workaround