Skip to content

Conversation

@jonseitz
Copy link
Contributor

@jonseitz jonseitz commented Jul 9, 2021

Describe your changes

The original button implementation had a disabled prop that prevented the onClick handler from being called, but did not include any stylistic changes to indicate to the user that the button was disabled. In fact the :hover and :active pseudo-classes were still being applied so it appeared as through the button was clicked but nothing was happening. This adds some additional style rules to the :disabled pseudo-class to provide visual cues to the user that the button is disabled.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality
    to change)

Checklist:

  • I have run eslint on the code
  • I have added JSDoc for all of my code (where applicable)
  • I have added tests to cover my changes.

Priority:

  • Normal
  • High

Related Issues:

Fixes #109

jonseitz added 2 commits July 8, 2021 16:30
Previously, setting a button as disabled only prevented the click
handler from firing; it did not make any style changes. For the casual
user, this presents as broken functionality rather than not-allowed
functionality.
Loops through our VARIANT enum to render each style of button
(including dupliacates) and shows the active and disabled styles
side-by-side
Base automatically changed from develop to main January 24, 2024 21:14
@natalynyu natalynyu changed the base branch from main to develop January 24, 2024 21:16
@jonseitz jonseitz marked this pull request as draft April 17, 2024 02:55
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