🎨 Palette: Add loading states to async auth buttons#184
Conversation
Implemented visual loading states and disabled logic for the Login, Register, and Google Sign-in buttons to prevent duplicate submissions and provide better user feedback during asynchronous authentication API requests. Restored element states safely within try/finally blocks. 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. |
1 participant
💡 What: Added visual loading states and disabled behavior to the Login, Register, and Google Sign-in buttons.
🎯 Why: To provide immediate user feedback during asynchronous API requests and prevent duplicate form submissions, a common failure point in vanilla JS implementations.
📸 Before/After: Before, the buttons remained interactive and visually unchanged while the network request processed. Now, they visibly update to a disabled state showing "⏳ Loading..." and reduced opacity until the promise resolves or rejects.
♿ Accessibility: Prevents keyboard and screen reader users from accidentally triggering the same form action multiple times, and clearly communicates application processing state.
PR created automatically by Jules for task 15575952195395858550 started by @singhaditya21