aboutsummaryrefslogtreecommitdiff
path: root/site/content/docs/5.1/components/card.md
AgeCommit message (Collapse)AuthorFilesLines
2022-05-13Prepare v5.2.0-beta1Mark Otto1-739/+0
2022-04-30Update badges, cards, and toasts to use new helpersMark Otto1-2/+4
2022-03-28Train PR: CSS variables for accordion, cards, navs, and modals (#36071)Mark Otto1-1/+9
* Convert accordion to CSS vars * Update accordion.md * Convert navs to CSS variables * Split up CSS vars * bundlewatch * fix vars * Convert cards to CSS vars * Convert modals to CSS variables * Bundlewatch Co-authored-by: Geremia Taglialatela <[email protected]>
2021-09-06Disabled link cleanup (#34886)Patrick H. Lauke1-2/+2
* Disabled link cleanup per https://www.w3.org/TR/html-aria/#docconformance > It is NOT RECOMMENDED to use `aria-disabled="true"` on an `a` element with an `href` attribute. > >NOTE >If a link needs to be "disabled", remove the `href` attribute. This PR removes the unnecessary `href="#"`, `tabindex="-1"`, and `aria-disabled="true"` from disabled links in both docs pages and examples. `aria-disabled="true"` *is* kept for disabled link-based buttons (that have `role="button"`) as there it's appropriate to use (you *want* to convey to assistive technologies that this thing you're claiming is a button is also disabled at the moment) Further, the PR extends the "Link functionality caveat" to show the "proper" way (removing `href` and adding `.disabled` class only) to disable a link, but then explains what to do if that's not possible (and then keeps an example with all the traditional `href="#" tabindex="-1" aria-disabled="true"`, but explains clearly that it's not ideal). Same sort of explanation is also added to the pointer event utilities page * Turn big note into actual normal doc text Co-authored-by: Mark Otto <[email protected]> Co-authored-by: Mark Otto <[email protected]> Co-authored-by: XhmikosR <[email protected]>
2021-08-04Prepare v5.1.0. (#34674)v5.1.0XhmikosR1-0/+729