🎨 Palette: Add loading states to authentication buttons - #193
🎨 Palette: Add loading states to authentication buttons#193singhaditya21 wants to merge 1 commit into
Conversation
Prevents duplicate submissions and improves UX feedback during login and registration. Co-authored-by: singhaditya21 <53948039+singhaditya21@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
💡 What
Added visual loading states to the Login, Registration, and Google Sign-in buttons. During form submission or authentication flows, the buttons are disabled and their text changes to "⏳ Loading...". The original state is reliably restored after the operation finishes using a
try/finallyblock.🎯 Why
Missing loading states on async operations lead to user confusion (e.g., wondering if the app registered their click) and can result in duplicate form submissions if users repeatedly click the button.
📸 Before/After
Before: Clicking "Sign In" provided no immediate visual feedback on the button itself while the network request resolved.
After: Clicking "Sign In" immediately disables the button and updates the text to indicate progress.
♿ Accessibility
disabled=true) prevents multiple screen reader announcements for repeated focus/clicks.PR created automatically by Jules for task 12700262907118727654 started by @singhaditya21