v5alpha LoadingButton rename to PendingButton?
See original GitHub issueI just used the LoadingButton to be a Submit button that will not become active until the user fills the form. IMHO better UX than having an active Submit button that tempts you to push it when you’re not supposed to 😉
So because your new button is can be great outside of just loading, perhaps a wider name like PendingButton
or StatusButton
could broaden its use…
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
v5alpha LoadingButton rename to PendingButton? #21906
I just used the LoadingButton to be a Submit button that will not become active until the user fills the form. IMHO better...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For this use case, prefer leaving the button pristine. We encourage end-users to be able to validate the form and trigger the validation errors, rather than starting with the button disabled.
Pending for the name of the state would better match what’s going on. Note that in 80% of the time (I don’t have any proof other than my experience building and using applications), what’s pending is a network request.
IMHO the whole tradeoff is about what’s more accurate vs what are developers more likely to find, expect, query. The balance is leaning toward the latter.
I’m locking the issue, it’s a duplicate of the one linked.