Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: improve/expand button documentation #31093

Merged
merged 6 commits into from
Jul 3, 2020

Conversation

patrickhlauke
Copy link
Member

  • since we're not doing the disabled cursor thing anymore anyway, remove confusing/unnecessary mention for link-based disabled buttons
  • make the disabled toggle example using a link actually follow the preceding advice of also having tabindex="-1" and aria-disabled="true"
  • tweak the link functionality callout to also still mention aria-disabled to reinforce the idea
  • tweak toggle state description (not just <button>s, but also links etc...so just remove mention of <button> there; also reinforce accessibility aspect once more)
  • add a new callout that cross-references checkbox-based toggles, and what the similarity/difference between them is
  • add a matching cross-reference callout to the checkbox-based toggle buttons page

- since we're not doing the disabled cursor thing anymore anyway, remove confusing/unnecessary mention for link-based disabled buttons
- make the disabled toggle example using a link actually follow the preceding advice of also having `tabindex="-1"` and `aria-disabled="true"`
- tweak the link functionality callout to also still mention `aria-disabled` to reinforce the idea
- tweak toggle state description (not just `<button>`s, but also links etc...so just remove mention of `<button>` there; also reinforce accessibility aspect once more)
- add a new callout that cross-references checkbox-based toggles, and what the similarity/difference between them is
- add a matching cross-reference callout to the checkbox-based toggle buttons page
@patrickhlauke patrickhlauke added this to Inbox in v5.0.0-alpha2 via automation Jun 21, 2020
Copy link
Member

@MartijnCuppens MartijnCuppens left a comment

Choose a reason for hiding this comment

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

LGTM

v5.0.0-alpha2 automation moved this from Inbox to Approved Jul 3, 2020
@patrickhlauke patrickhlauke merged commit 0a6cf90 into main Jul 3, 2020
v5.0.0-alpha2 automation moved this from Approved to Shipped Jul 3, 2020
@patrickhlauke patrickhlauke deleted the v5-docs-components-buttons branch July 3, 2020 11:34
olsza pushed a commit to olsza/bootstrap that referenced this pull request Oct 3, 2020
* Docs: improve/expand button documentation

- since we're not doing the disabled cursor thing anymore anyway, remove confusing/unnecessary mention for link-based disabled buttons
- make the disabled toggle example using a link actually follow the preceding advice of also having `tabindex="-1"` and `aria-disabled="true"`
- tweak the link functionality callout to also still mention `aria-disabled` to reinforce the idea
- tweak toggle state description (not just `<button>`s, but also links etc...so just remove mention of `<button>` there; also reinforce accessibility aspect once more)
- add a new callout that cross-references checkbox-based toggles, and what the similarity/difference between them is
- add a matching cross-reference callout to the checkbox-based toggle buttons page

* Update link to now renamed checks-radios.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
v5.0.0-alpha2
  
Shipped
Development

Successfully merging this pull request may close these issues.

None yet

2 participants