1. 17 Aug, 2017 2 commits
  2. 11 Aug, 2017 2 commits
  3. 04 Jul, 2017 1 commit
  4. 15 Jun, 2017 1 commit
    • Mark Otto's avatar
      Rename popover classes · 9c0e4230
      Mark Otto authored
      Part of an update to align the naming schemes across our components.
      
      - Renames .popover-title to .popover-header
      - Renames .popover-content to .popover-body
      
      Refs: #22092
      9c0e4230
  5. 14 Jun, 2017 2 commits
  6. 27 May, 2017 1 commit
  7. 14 May, 2017 4 commits
  8. 26 Apr, 2017 1 commit
  9. 25 Apr, 2017 1 commit
  10. 20 Apr, 2017 1 commit
  11. 17 Apr, 2017 1 commit
    • Patrick H. Lauke's avatar
      Fix carousel "hover" behavior on touch-enabled devices · 6ae5fb12
      Patrick H. Lauke authored
      * Add carousel mouse listeners even if touch events enabled
      
      - touch events are enabled not just on "mobile", just also on
      touch-enabled desktop/laptop devices; additionally, it's possible to
      pair a mouse with traditionally touch-only devices (e.g. Android
      phones/tablets); currently, in these situations the carousel WON'T pause
      even when using a mouse
      
      * Restart cycle after touchend
      
      as `mouseenter` is fired as part of the touch compatibility events, the
      previous change results in carousels which cycle until the user
      tapped/interacted with them. after that they stop cycling (as
      `mouseleave` is not sent to the carousel after user scrolled/tapped
      away).
      this fix resets the cycling after `touchend` - essentially returning
      to the previous behavior, where on touch the carousel essentially never
      pauses, but now with the previous fix it at least pauses correctly for
      mouse users on touch-enabled devices.
      includes documentation for this new behavior.
      6ae5fb12
  12. 10 Apr, 2017 2 commits
    • Patrick H. Lauke's avatar
      Fix collapse.js aria-expanded behavior · 18e87042
      Patrick H. Lauke authored
      * Remove aria-expanded from collapse.js target element
      
      aria-expanded="true"/aria-expanded="false" only applies to the trigger,
      not the element that is being expanded/collapsed.
      
      * Tweak collapse.js accessibility section
      
      ...to make it clearer that the aria-expanded attribute always just goes
      on the control.
      
      * Fix collapse.js unit tests
      
      - reword some of the text to make it clear we're checking behavior of
      trigger/control
      - move incorrect aria-expanded out of the <div>s and to the actual
      trigger/control <a>s
      - fix incorrect test assertion text output false -> true
      
      18e87042
    • Patrick H. Lauke's avatar
      Only change aria-pressed if it's not an input-based radio or checkbox group · 3f6e1faf
      Patrick H. Lauke authored
      * Only change aria-pressed if it's not an input-based radio or checkbox group
      
      aria-pressed="true"/aria-pressed="false" is really only useful for
      making on/off toggles out of, say, `<button>` elements. the attribute is
      useless (and potentially confusing/conflicting) on, say, `<label>`
      elements for an existing `<input type="radio">` or similar.
      
      * Add unit test for buttons.js and radio/checkbox inputs in button groups
      3f6e1faf
  13. 03 Apr, 2017 1 commit
  14. 02 Apr, 2017 2 commits
  15. 31 Mar, 2017 1 commit
  16. 28 Mar, 2017 2 commits
  17. 27 Mar, 2017 1 commit
  18. 23 Mar, 2017 1 commit
  19. 22 Mar, 2017 1 commit
  20. 21 Mar, 2017 1 commit
  21. 18 Mar, 2017 1 commit
  22. 09 Mar, 2017 1 commit
  23. 08 Feb, 2017 1 commit
  24. 21 Jan, 2017 4 commits
  25. 06 Jan, 2017 1 commit
  26. 04 Jan, 2017 1 commit
  27. 02 Jan, 2017 2 commits