3 ms·
>A good example are pages that take 5 seconds to load because they have to do so much, then you submit a form, and the page reload takes 5 seconds to go through
by leptons 1y ago
>A good example are pages that take 5 seconds to load because they have to do so much, then you submit a form, and the page reload takes 5 seconds to go through but there is no UI feedback so you press the button a few more times because maybe it didn’t work? Then you get an error because the first action worked but the subsequent actions failed due to uniqueness constraints.
It's been standard practice for at least 25 years to disable the submit button once it is pressed. If you aren't doing this as a developer, you are practically begging for trouble, and it's really so easy to avoid that trouble.
- Swizec 1y agoLots of people build stuff and don’t have 25 years of experience. Or it seemed like “unnecessary complexity” when the app had 5 users and interactions took 100ms. A lot of standard things feel like “wow people are way overthinking this, it’s so easy” when you have 5 users :)
- leptons 1y agoWhoever taught them wasn't doing their job well.
- NohatCoder 1y agoAt least adding in the feature once you notice the problem shouldn't be difficult.
- ardleon 1y agoOr disable the component completely until you receive a response.