Discourse-boosts Float-Kit will close unexpectly when triggering keyboard on iOS devices

AI-generated summary

small-lovely-cat reports a bug in the Discourse-boosts Float-Kit where the interface unexpectedly closes on iOS devices when the keyboard is triggered. This behavior causes the page to scroll repeatedly, making it extremely difficult to input text. The issue is linked to pull request 19 and affects iOS specifically, unlike other devices. awesomerobot acknowledges the report and confirms that a fix is already in the queue via pull request 21.

This bug is related to UX: auto close FloatKit menu on page scroll - Pull Request #19 - discourse/discourse-boosts - GitHub, while it works well on other devices, it make inputting broken on iOS devices.

When we click the input area of boosts, iOS will trigger keyboard and make the page scroll, and the boost Float-Kit will close, and this get repeated until the input element is on a specific area, making inputting extreme difficult.

Not sure how to solve that, maybe blocking this behavior for iOS devices?

1 Like

Thanks for reporting it! I’ve got a fix in our queue here

The change prevents the menu from closing when the input is focused, which fixes the initial open and still allows the menu to close when scrolling otherwise.

1 Like