🎨 Palette: Add visual feedback for disabled buttons - #56
Conversation
Fixed an issue where buttons disabled by Vue directives (like `:disabled="isSending"`) did not show any visual feedback and still responded to hover animations. Applied `opacity: 0.5`, `cursor: not-allowed` globally to `.button:disabled`, and disabled `transform` animations using `:not(:disabled)`. Co-authored-by: MEKXH <59291264+MEKXH@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 specific styles for
.button:disabledand restricted the.button:hovertransition animation from executing on disabled components inweb/src/styles.css.🎯 Why: When buttons like "Send" and "Check Gateway" were disabled during active processing (
isSending,isChecking), they looked and hovered exactly like active buttons. This causes user confusion because actions appear clickable when they are not.📸 Before/After: See attached Playwright verification logs where the disabled buttons now appear faded globally across the
ComposerPaneland elsewhere.♿ Accessibility: Provides much-needed visual distinction, clearly communicating the un-interactable element state to sighted users according to the
aria-disabled/disabledattribute context.PR created automatically by Jules for task 3082447729256737819 started by @MEKXH