Skip to content

fix(site): keep standard avatar border for normal AI spend state - #28037

Open
tracyjohnsonux wants to merge 4 commits into
mainfrom
tracyjohnsonux/avatar-spend-border-normal-state
Open

fix(site): keep standard avatar border for normal AI spend state#28037
tracyjohnsonux wants to merge 4 commits into
mainfrom
tracyjohnsonux/avatar-spend-border-normal-state

Conversation

@tracyjohnsonux

@tracyjohnsonux tracyjohnsonux commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

The navbar avatar received a grey border-content-secondary override whenever AI spend data was present, so the default (normal spend) state looked different from a standard avatar. It also relied entirely on border color to communicate state, which is easy to miss and inaccessible to colorblind users.

Changes

  • Normal state: no border override — the avatar keeps the standard Avatar border.
  • Warning / exceeded states:
    • Thicker border-2 in the warning/destructive color, so the state change is perceivable by thickness as well as color.
    • A small notification-style dot on the avatar corner, so there is an explicit "something to look at" indicator rather than only an ambient border change.
    • Tooltip and screen-reader label ("AI spend is nearing its limit" / "AI spend limit exceeded") on the avatar trigger.

Storybook: AvatarBorderNormal/Warning/Exceeded stories now assert indicator presence/absence, and Chromatic snapshots cover the visual states.


This PR was generated by Coder Agents on behalf of @tracyjohnsonux.

The user dropdown avatar previously received a grey border override
whenever spend data was present, even in the normal state. Keep the
default avatar border for normal spend and only change the border for
warning/exceeded states, using a thicker 2px border so the change is
perceivable without relying on color alone.
Elevated spend states now show a corner badge with a warning icon and
an accessible label/tooltip, so the state change does not rely on the
border color alone.
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