Skip to content

🎨 Palette: Fix lingering status bar states and tooltips#90

Draft
raccioly wants to merge 1 commit intomainfrom
palette-status-bar-ux-8007343808529796959
Draft

🎨 Palette: Fix lingering status bar states and tooltips#90
raccioly wants to merge 1 commit intomainfrom
palette-status-bar-ux-8007343808529796959

Conversation

@raccioly
Copy link
Copy Markdown
Owner

@raccioly raccioly commented May 7, 2026

💡 What

This micro-UX improvement ensures that the DocGuard VS Code extension's status bar resets correctly and provides actionable tooltips when entering an unknown or errored state.

🎯 Why

In VS Code, status bar backgroundColor values (e.g., warningBackground and errorBackground) persist until manually cleared. Previously, if a user received a failing score (turning the background red/yellow) and then the extension ran into an unexpected error parsing the score, the status text would update to $(shield) CDD: ? but the background color would remain visually alarming, misleading the developer.

Additionally, static tooltips failed to inform the user why they were seeing an unknown state.

📸 Before/After

Before:

  • CDD score parsing error happens after a failure.
  • Status bar says: $(shield) CDD: ? with a bright warning background color.
  • Tooltip says: Click to see CDD score details.

After:

  • CDD score parsing error happens after a failure.
  • Status bar says: $(shield) CDD: ? with a neutral (cleared) background color.
  • Tooltip says: CDD Score Error: [error msg]. Click to retry or CDD Score: Unknown. Click to try refreshing.

♿ Accessibility

This change improves visual feedback clarity and ensures screen reader users (reading the tooltip text on focus) and visually impaired users navigating via keyboard get explicitly descriptive, state-relevant context rather than generic unhelpful text.


PR created automatically by Jules for task 8007343808529796959 started by @raccioly

- Reset `statusBarItem.backgroundColor` for unknown/error states
- Map status bar elements to context-aware tooltips instead of static text
- Mark `activate` as async to fix strict Node.js validation

Co-authored-by: raccioly <63126795+raccioly@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 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