You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to how we made the task collection button not clickable twice while waiting on server feedback, we should do this for other buttons as well.
This came up because it was possible (due to some performance issues in 1.4.1) for users to submit the same job multiple times by clicking the Confirm button in "Run workflow" multiple times. We should think about whether other buttons also could have this issue where it would matter.
I don't care too much about behaviors that would be unproblematic. e.g. download job logs: If a user clicks that 5x, they may get the job logs 5 times. But nothing breaks.
Buttons to deactivate after click until server response:
Confirm job submission
Task updating (on the workflow page)
Maybe project creation?
Maybe dataset creation?
Maybe workflow creation/import?
Not 100% sure whether it makes sense for the new creation buttons / how they'd handle multiple clicks if the server response was very slow
The text was updated successfully, but these errors were encountered:
Similar to how we made the task collection button not clickable twice while waiting on server feedback, we should do this for other buttons as well.
This came up because it was possible (due to some performance issues in 1.4.1) for users to submit the same job multiple times by clicking the Confirm button in "Run workflow" multiple times. We should think about whether other buttons also could have this issue where it would matter.
I don't care too much about behaviors that would be unproblematic. e.g. download job logs: If a user clicks that 5x, they may get the job logs 5 times. But nothing breaks.
Buttons to deactivate after click until server response:
Not 100% sure whether it makes sense for the new creation buttons / how they'd handle multiple clicks if the server response was very slow
The text was updated successfully, but these errors were encountered: