1. 14 May, 2017 1 commit
  2. 26 Apr, 2017 1 commit
  3. 25 Apr, 2017 1 commit
  4. 20 Apr, 2017 1 commit
  5. 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
  6. 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
  7. 03 Apr, 2017 1 commit
  8. 02 Apr, 2017 2 commits
  9. 31 Mar, 2017 1 commit
  10. 28 Mar, 2017 2 commits
  11. 27 Mar, 2017 1 commit
  12. 23 Mar, 2017 1 commit
  13. 22 Mar, 2017 1 commit
  14. 21 Mar, 2017 1 commit
  15. 18 Mar, 2017 1 commit
  16. 09 Mar, 2017 1 commit
  17. 08 Feb, 2017 1 commit
  18. 21 Jan, 2017 4 commits
  19. 06 Jan, 2017 1 commit
  20. 04 Jan, 2017 1 commit
  21. 02 Jan, 2017 2 commits
  22. 31 Dec, 2016 1 commit
  23. 29 Dec, 2016 1 commit
  24. 27 Dec, 2016 1 commit
  25. 25 Dec, 2016 1 commit
  26. 23 Dec, 2016 1 commit
    • Matheus Azzi's avatar
      Carousel: Only prevents default for ARROW_LEFT and ARROW_RIGHT keys · dab6a41e
      Matheus Azzi authored
      Fixes 2 bugs:
      
      1. All keydowns were being prevented. Because of that the user wasn't able to navigate in the whole page using ARROW_UP/ARROW_DOWN.
      
      2. Even when  is an input or textarea the keydowns were being prevented. Because of that the user wasn't able to type any text on these elements.
      dab6a41e
  27. 08 Dec, 2016 1 commit
  28. 28 Nov, 2016 1 commit
    • Rob Ruana's avatar
      Closes #21055: Prevents ScrollSpy from clearing active item when Safari rubberbands (#21056) · 5eddb0b0
      Rob Ruana authored
      When the rubberband effect causes Safari to scroll past the top of the
      page, the value of scrollTop becomes negative. If the offset of the first
      ScrollSpy target is 0 - essentially if the target is at the top of the
      page - then ScrollSpy should not clear the active item. Conceptually, the
      first item should remain active when rubberbanding past the top of the
      page.
      
      This commit fixes issue #21055 by verifying the first scrollspy target is
      not at the top of the page before clearing the active nav-item.
      5eddb0b0
  29. 26 Nov, 2016 1 commit
  30. 25 Nov, 2016 1 commit
  31. 24 Nov, 2016 1 commit
  32. 01 Nov, 2016 1 commit
  33. 25 Oct, 2016 1 commit