1. 28 Oct, 2021 1 commit
    • XhmikosR's avatar
      Update devDependencies (#35271) · 3f883268
      XhmikosR authored
      * autoprefixer  ^10.3.7  →  ^10.4.0
      * eslint         ^8.0.1  →   ^8.1.0
      * karma          ^6.3.5  →   ^6.3.6
      * rollup        ^2.58.0  →  ^2.58.3
      3f883268
  2. 22 Oct, 2021 6 commits
  3. 21 Oct, 2021 1 commit
  4. 05 Oct, 2021 1 commit
  5. 28 Sep, 2021 2 commits
  6. 15 Sep, 2021 15 commits
  7. 14 Sep, 2021 1 commit
  8. 09 Sep, 2021 1 commit
    • Patrick H. Lauke's avatar
      v4: Disabled link cleanup (#34924) · f4a1a35c
      Patrick H. Lauke authored
      manual backport of #34886
      
      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
      f4a1a35c
  9. 08 Sep, 2021 3 commits
  10. 25 Jul, 2021 1 commit
  11. 21 Jul, 2021 8 commits