Skip to content

fix(avatar-button): Keep the default button frame around avatars - #130893

Draft
priscilawebdev wants to merge 6 commits into
masterfrom
priscilawebdev/fix/avatar-button-neutral-frame
Draft

priscilawebdev wants to merge 6 commits into
masterfrom
priscilawebdev/fix/avatar-button-neutral-frame

Conversation

@priscilawebdev

@priscilawebdev priscilawebdev commented Nov 12, 2026 •

Copy link
Copy Markdown
Member

AvatarButton no longer colors its frame from the avatar. The border and raised edge used a color sampled from the image (or derived from the letter-avatar swatch); every avatar button now uses the default neutral button frame, as in the Settings v3 design. This affects every AvatarButton in the app, including the primary navigation and assignee pickers.

The avatar container also used to draw a transparent border on top of the button's own border whenever there was no sampled color, so the button lost its outline. It now draws that border in the button's edge color (interactive.chonky.embossed.neutral.chonk), so avatar buttons have the same outline as other buttons.

Unchanged: logos that don't fill the frame are still inset with padding, and suggested assignees keep their dashed neutral border.

With the frame color gone, useAvatarColors and the image analysis no longer compute it, and the 3:1 contrast tuning that only served it (darkenUntilContrasts) is removed. The sampling still returns the avatar's dominant color, which the menu header gradient uses, and whether a logo should be inset.

The menu header gradient is handled separately in #130236.

Refs DE-1832

The button's border and raised edge took a color sampled from the avatar, and the container drew a transparent border over the button's own when there was none. The Settings v3 design uses the default neutral button frame for every avatar, so draw the container border in the button's edge color and stop sampling a frame color. Logos that don't fill the frame are still inset.

Refs DE-1832
@linear-code

linear-code Bot commented Nov 12, 2026

Copy link
Copy Markdown

DE-1832

@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 12, 2026
Nothing reads chonk now that the button keeps its default frame. Remove it from useAvatarColors and the image analysis, along with the contrast tuning that only served it. The sampling still returns the dominant color for the menu header gradient and whether a logo should be inset.

Refs DE-1832
@github-actions

github-actions Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Story previews

Preview the stories changed in this PR on the Vercel deployment:

Preview deployment: https://sentry-5um3hqub6.sentry.dev

…tons

Only the organization and user buttons in the primary navigation should drop the avatar-colored frame. Add frame="neutral" to AvatarButton, which keeps the default button frame and redraws its border around the avatar, and use it for those buttons. Every other AvatarButton keeps the frame sampled from the avatar.

Refs DE-1832

This branch was successfully deployed

1 active deployment
Preview — 1ef25aba Deployed Nov 12, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant