If you aren’t actually using the input in an action, then you can create a state on the page and then save the input’s value there, then reset the relevant input. This forces the input to clear out.
You can force the keyboard to hide by conditionally setting the relevant input to “this input is disabled”. @johnny
So for example in my case, I don’t need the input anymore when the sheet gets closed, so I’ve just set the input condition to “When Sheet “X” isn’t visible → This input is disabled”
I don’t think this approach is ideal though. I think Bubble should know when an input gets hidden, and automatically close the keyboard
yep we hear you, definitely not ideal. Adding in a dismiss keyboard action, whether via workflow or on the keyboard itself, is on our radar, but lower prio than a lot of the bug fixing & build stability work the team is currently working on