All Versions
81
Latest Version
Avg Release Cycle
64 days
Latest Release
56 days ago

Changelog History
Page 7

  • v0.8.4 Changes

    October 15, 2015
    • ๐Ÿ›  Bugfix: SVG elements now properly use transform attribute instead of style. Thanks @martinRoss
  • v0.8.3 Changes

    October 12, 2015
    • ๐Ÿ›  Bugfix: Short-circuiting drag throws due to e.changedTouches check.
  • v0.8.2 Changes

    September 21, 2015
    • ๐Ÿ– Handle scrolling while dragging. (#60)
    • โž• Add multi-touch support. (#68)
    • ๐Ÿ›  IE fixes.
    • ๐Ÿ“š Documentation updates. (#77)
  • v0.8.1 Changes

    June 03, 2015
    • โž• Add resetState() instance method for use by parents. See README ("State Problems?").
  • v0.8.0 Changes

    May 19, 2015
    • ๐Ÿ›  Touch/mouse events rework. Fixes #51, #37, and #43, as well as IE11 support.
    • ๐Ÿšš Moved mousemove/mouseup and touch event handlers to document from window. Fixes IE9/10 support. IE8 is still not supported, as it is not supported by React.
  • v0.7.4 Changes

    May 18, 2015
    • ๐Ÿ›  Fix a bug where a quick drag out of bounds to 0,0 would cause the element to remain in an inaccurate position, because the translation was removed from the CSS. See #55.
  • v0.7.3 Changes

    May 13, 2015
  • v0.7.2 Changes

    May 08, 2015
    • โž• Added moveOnStartChange property. See README.
  • v0.7.1 Changes

    May 07, 2015
    • The start param is back. Pass {x: Number, y: Number} to kickoff the CSS transform. Useful in certain cases for simpler callback math (so you don't have to know its existing relative position and add it to the dragged position). Fixes #52.
  • v0.7.0 Changes

    May 07, 2015
    • ๐Ÿ’ฅ Breaking change: bounds with coordinates was confusing because it was using the item's width/height, which was not intuitive. When providing coordinates, bounds now simply restricts movement in each direction by that many pixels.