Skip to content

chore(Upgrade guide): removed verbiage on button aria-disabled#4494

Merged
edonehoo merged 3 commits intopatternfly:mainfrom
thatblindgeye:upgradeAriaDisabledButton
Mar 12, 2025
Merged

chore(Upgrade guide): removed verbiage on button aria-disabled#4494
edonehoo merged 3 commits intopatternfly:mainfrom
thatblindgeye:upgradeAriaDisabledButton

Conversation

@thatblindgeye
Copy link
Copy Markdown
Contributor

@patternfly-build
Copy link
Copy Markdown
Collaborator

patternfly-build commented Mar 10, 2025

@thatblindgeye thatblindgeye requested a review from tlabaj March 11, 2025 15:25
@thatblindgeye thatblindgeye force-pushed the upgradeAriaDisabledButton branch from 087fd4b to b075f66 Compare March 12, 2025 12:32
@thatblindgeye thatblindgeye requested a review from edonehoo March 12, 2025 12:32
@thatblindgeye
Copy link
Copy Markdown
Contributor Author

@edonehoo would you mind taking a look at this update? i originally put this PR up before one of yours went in that updated this page a bit and just pushed a tweak based on a convo Titani and I had yesterday.

Copy link
Copy Markdown
Contributor

@tlabaj tlabaj left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link
Copy Markdown
Collaborator

@edonehoo edonehoo left a comment

Choose a reason for hiding this comment

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

I left a couple of options for line 176, because I wasn't 100% sure if I was reading that right. If both are wrong, lmk 😅

1. *Cannot find aria-disabled*
- **Cause:** We changed the `isDisabled` prop to assign a value for `disabled`, but none for `aria-disabled`.
- **Fix:** Remove tests that look for `aria-disabled` in buttons.
- **Cause:** We changed button's `isDisabled` prop to assign a value for `disabled`, but none for `aria-disabled` - except for when the `component` prop is passed anything other than "button" as a value. Additionally, `aria-disabled` will now only render when true.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
- **Cause:** We changed button's `isDisabled` prop to assign a value for `disabled`, but none for `aria-disabled` - except for when the `component` prop is passed anything other than "button" as a value. Additionally, `aria-disabled` will now only render when true.
- **Cause:** We changed button's `isDisabled` prop to assign a value for `disabled`, but none for `aria-disabled`. The exception to this is when the `component` prop is passed anything other than "button" as a value. Additionally, `aria-disabled` will now only render when true.

- **Cause:** We changed the `isDisabled` prop to assign a value for `disabled`, but none for `aria-disabled`.
- **Fix:** Remove tests that look for `aria-disabled` in buttons.
- **Cause:** We changed button's `isDisabled` prop to assign a value for `disabled`, but none for `aria-disabled` - except for when the `component` prop is passed anything other than "button" as a value. Additionally, `aria-disabled` will now only render when true.
- **Fix:** Remove tests that look for `aria-disabled` in buttons when the expectation is for it to be false, or to match `isDisabled` when `component="button"`.
Copy link
Copy Markdown
Collaborator

@edonehoo edonehoo Mar 12, 2025

Choose a reason for hiding this comment

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

Suggested change
- **Fix:** Remove tests that look for `aria-disabled` in buttons when the expectation is for it to be false, or to match `isDisabled` when `component="button"`.
- **Fix:** Remove tests that look for `aria-disabled` in buttons when the expectation is either:
- For `aria-disabled` to be false.
- For `aria-disabled` to match `isDisabled` when `component="button"`.

I'm not sure if I'm correctly interpreting the end of the sentence. I took it like there are 2 instances where you should remove these tests (the suggestion above and also below)

I can also interpret it like this:

Fix: Either:
- Remove tests that look for aria-disabled in buttons, when the expectation is for aria-disabled to be false.
- Match aria-disabled to isDisabled when component="button".

@edonehoo edonehoo merged commit 9e50370 into patternfly:main Mar 12, 2025
4 checks passed
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.

4 participants