Skip to content

🎨 Palette: [UX improvement] Semantic Error Colors in TUI Footer - #62

Open
omsingh02 wants to merge 1 commit into
mainfrom
palette-semantic-error-colors-1916898909420506889
Open

🎨 Palette: [UX improvement] Semantic Error Colors in TUI Footer#62
omsingh02 wants to merge 1 commit into
mainfrom
palette-semantic-error-colors-1916898909420506889

Conversation

@omsingh02

Copy link
Copy Markdown
Owner

💡 What

Updated the TUI's footer rendering (_make_footer in src/ui/tui.py) to properly check if the application status indicates an error. If an error is detected (via the presence of "[!]" or "error"), the footer displays a semantic red indicator and border instead of falling back to default styling.

🎯 Why

Terminal interfaces often rely on generic color fallbacks (e.g., green for all unrecognized states), which can mistakenly present error messages with "success" visual cues. This small modification ensures that error messages provide immediate, accurate visual feedback.

📸 Before/After

  • Before: A voice error like [!] Voice error: ... would be rendered in the footer with a green and a cyan border.
  • After: The same error is now rendered with a bold red and a red border for clear, immediate communication of the failure.

♿ Accessibility

Improves visual communication by aligning semantic meaning (error) with the appropriate color cue (red), ensuring users quickly recognize when an action has failed without solely relying on reading the text.


PR created automatically by Jules for task 1916898909420506889 started by @omsingh02

- Dynamically check status strings for error indicators (e.g., "[!]", "error").
- Apply semantic red styling to footer indicators and borders during error states.
- Prevents fallback to default/success styling on errors.

Co-authored-by: omsingh02 <215121080+omsingh02@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant