How do you handle input spam

When users are entering input or pressing buttons, how do you handle issues where the page is busy so the button press isn't registered right away, or where the user clicks the button multiple times causing the result to recalculate multiple times?

One possibility is the way the bslib package is handlig it Button for launching longer-running operations — input_task_button • bslib. They don't allow for multiple triggers of the button but show you an animation indicating that the process is currently executing. In this way the user is also informed on the current status of the process.

1 Like