This PR closes no issue, but is a pre-burner to #3681
What is the new behavior?
Add support for aria-disabled on Button component:
Setting aria-disabled="true" on the Button component will render the button as disabled and prevent activation through mouse, touch and keyboard but still allow the button to be focused and therefore percieveable.
Does this PR introduce a breaking change?
[ ] Yes
[x] No
Are there any additional context?
Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Reminders
[x] Make sure you have implemented tests following the guidelines in: "The good: Test".
[x] Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).
Review
[x] Determine if your changes are a fix, feature or breaking-change, and add the matching label to your PR. If it is tooling, dependency updates or similar, add ignore-for-release.
Which issue does this PR close?
This PR closes no issue, but is a pre-burner to #3681
What is the new behavior?
Add support for
aria-disabledonButtoncomponent:Setting
aria-disabled="true"on theButtoncomponent will render the button as disabled and prevent activation through mouse, touch and keyboard but still allow the button to be focused and therefore percieveable.Does this PR introduce a breaking change?
Are there any additional context?
Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Reminders
Review
When the pull request has been approved it will be merged to
developby Team Kirby.