Skip to content

🎨 Palette: Improve status bar state transitions#97

Draft
raccioly wants to merge 1 commit intomainfrom
palette/fix-vscode-status-bar-ux-4385439644776734721
Draft

🎨 Palette: Improve status bar state transitions#97
raccioly wants to merge 1 commit intomainfrom
palette/fix-vscode-status-bar-ux-4385439644776734721

Conversation

@raccioly
Copy link
Copy Markdown
Owner

@raccioly raccioly commented May 9, 2026

💡 What

Updated the VS Code extension to explicitly reset the status bar background color to undefined when the CDD score check fails or enters an unknown state. Also added descriptive tooltips to explicitly indicate 'Unknown' or 'Error' states, and fixed a syntax error by converting the activate function to async.

🎯 Why

In the VS Code API, custom background colors (like warningBackground) persist across state updates unless explicitly reset. If an error occurs, a previous warning state's color could linger, providing confusing and inaccurate visual feedback to the developer. The added tooltips ensure developers have context for the status bar icon.

📸 Before/After

  • Before: If the CLI threw an error after previously scoring < 60, the status bar would display the fallback icon ($(shield) CDD: ?) but remain colored warning yellow/red, with no explanation in the tooltip.
  • After: The status bar clears the warning background and provides a tooltip reading "CDD Score: Error\nClick to see details" or "CDD Score: Unknown", making the current state immediately clear.

♿ Accessibility

Improves accessibility by ensuring visual color cues accurately match the system's underlying state, and by providing explicit text via tooltips for users who may rely on screen readers or hover interactions rather than color alone to deduce status.


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

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