🎨 Palette: Add async loading states to authentication forms#179
🎨 Palette: Add async loading states to authentication forms#179singhaditya21 wants to merge 1 commit into
Conversation
Adds visually distinct and structurally sound loading states to the Login and Registration forms. When submitted, the buttons now fade gracefully to 70% opacity, update their text to reflect the action ("Signing in..." / "Signing up..."), disable the cursor, and disable the button itself to prevent double submissions. This state is safely unwound in a finally block ensuring the UI never gets permanently stuck.
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 immediate visual feedback for the async Login and Register forms. During the submission process, the submit button is disabled, slightly faded, and its text changes to indicate work is happening (e.g., "Signing in...").
🎯 Why
Without loading states, users might be confused about whether their click registered, especially if the API response is slow. This often leads to users mashing the submit button repeatedly, potentially causing duplicate account creation requests or unexpected UI errors. Giving immediate feedback reassures the user.
📸 Before/After
(Visuals verified via frontend testing tool)
Before: Clicking "Sign In" or "Sign Up" resulted in no immediate visual change to the button; the app silently waited for the network request to finish.
After: The button instantly greys out slightly, disables itself, and updates its text to "Signing in..." or "Signing up..." until the request completes or errors out.
♿ Accessibility
This improvement adds standard HTML disabled states to the buttons during processing. Screen readers that announce state changes will correctly identify that the button can temporarily no longer be interacted with, reducing confusion for visually impaired users about whether they need to activate the button again.
PR created automatically by Jules for task 16103145342047572974 started by @singhaditya21