Skip to content

feat(button): Busy spinner with absolute position#110202

Draft
TkDodo wants to merge 2 commits intomasterfrom
tkdodo/feat/de-980-busy-state
Draft

feat(button): Busy spinner with absolute position#110202
TkDodo wants to merge 2 commits intomasterfrom
tkdodo/feat/de-980-busy-state

Conversation

@TkDodo
Copy link
Collaborator

@TkDodo TkDodo commented Mar 9, 2026

this is the 3rd attempt to land de-980 after two reverts. This approach does not change the button internal layout to avoid the large blast radius of the first two approaches.

@linear-code
Copy link

linear-code bot commented Mar 9, 2026

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Mar 9, 2026
Copy link
Member

@natemoo-re natemoo-re left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Conceptually approved! Didn't see any visual errors in the preview 🙌

Would love to see the button docs updated and another once-over on the aria states for the entire component.

visibility="visible"
>
{({className}) => (
<BusySpinner className={className} role="status" aria-label="Busy" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My preference would be to set the button's aria-label to Submitting rather than the spinner.

Found some interesting a11y insights that seem relevant!

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.

2 participants