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

**URL:** <https://meta.discourse.org/t/discourse-boosts-float-kit-will-close-unexpectly-when-triggering-keyboard-on-ios-devices/413770>\
**Category:** Bug\
**Created:** [October 2, 2026, 5:38am UTC](https://meta.discourse.org/t/discourse-boosts-float-kit-will-close-unexpectly-when-triggering-keyboard-on-ios-devices/413770 "2026-10-02T05:38:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![small-lovely-cat](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/small-lovely-cat/32/579066_2.png) [@small-lovely-cat](https://meta.discourse.org/u/small-lovely-cat)\
**Post date:** [October 2, 2026, 5:38am UTC](https://meta.discourse.org/t/discourse-boosts-float-kit-will-close-unexpectly-when-triggering-keyboard-on-ios-devices/413770/1 "2026-10-02T05:38:48Z")

</div>

This bug is related to [UX: auto close FloatKit menu on page scroll - Pull Request #19 - discourse/discourse-boosts - GitHub](https://github.com/discourse/discourse-boosts/pull/19), 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?