[Android] Topic control dropdown activates keyboard

[daath (Lars)]

One of my users notified me that when you use Android and activate the “topic control”-dropdown, the keyboard activates, even though you can’t input anything anywhere. I confirmed it on my S8+ with Oreo using Chrome.

[jomaxro (Joshua Rosenfeld)]

I can repro this as well. Not just “Topic Controls” but also the notification state controls. cc @j.jaffeux.

[daath (Lars)]

As a side note, pressing the wrench icon brings up admin tools (if you’re admin) - doesn’t look like you can fold that one back, and it looks weird when scrolling over a youtube onebox (the title of the youtube box is over the admin panel)…

[j.jaffeux (Joffrey Jaffeux)]

Fixed by

https://github.com/discourse/discourse/commit/11c47f57f9458422467da8ba6d690d6a31cfa1c0

Thanks.

[supermathie (Michael Brown)]

This has reverted for me on Android / Chrome 68 and Chrome 68 Beta - when selecting Topic Controls or Tracking options the keyboard pops up.

[jomaxro (Joshua Rosenfeld)]

Also affects:

• all drop downs in the topic timer modal
• the category and tag drop downs in the composer
• category, subcategory, and tag filters above the topic list
• time range selector above /top and /u

[codinghorror (Jeff Atwood)]

Still pretty narrow for most users.

I can repro on my fully up to date Android device. Any ideas @j.jaffeux?

[j.jaffeux (Joffrey Jaffeux)]

I pushed a fix which I think is fixing it. I tested it on an android device with chrome 68 and could reproduce before, and not after this fix. Let me know if it works for you @supermathie please.

[jomaxro (Joshua Rosenfeld)]

Looks good to me. No more keyboard pop up on topic timer modal, topic controls, or the time range selectors. Still seeing the keyboard appear on the category and tag drop downs in the composer and filters above the topic list, but I’m pretty sure that pre-dated this regression. Those drop downs/filters have an actual search field that is gaining focus, likely calls for its own topic.

[supermathie (Michael Brown)]

All better for me! Thanks!

[jomaxro (Joshua Rosenfeld)]

Yep, looks great now! Thanks for your work on this @j.jaffeux

[j.jaffeux (Joffrey Jaffeux)]

It’s kind of hard to automate testing on this sadly Thanks for looking at it. I learned a lot since I started writing select-kit and will need to dedicate some time in the future to improve all of this. There are a lot of things I could write in a better and safer ways now.