react-draggable

Frameworks & LibrariesMIT

react-draggable release notes.

Latest v2.2.3 · by react-draggableWritten in JavaScriptWebsitereact-grid-layout/react-draggableRSS

Changelog

v2.2.3Latest

2.2.3

Fixed 1
  • Fix an issue with the entire window scrolling on a drag on iDevices

From react-draggable

  • Bugfix: Fix an issue with the entire window scrolling on a drag on iDevices. Thanks @JaneCoder. See #183
View originalPermalink
How v2.2.3 went
v2.2.2

2.2.2

Fixed 2
  • Fix references to global when grabbing SVGElement
  • Get ownerDocument before onStop

From react-draggable

  • Bugfix: Fix references to global when grabbing SVGElement, see #162
  • Bugfix: Get ownerDocument before onStop, fixes #198
View originalPermalink
How v2.2.2 went
v2.2.1

2.2.1

Fixed 1
  • Fix getComputedStyle error

From react-draggable

  • Bugfix: Fix getComputedStyle error: see #186, #190
View originalPermalink
How v2.2.1 went
v2.1.2

2.1.2

Fixed 1
  • Fix `return false` to cancel `onDrag` breaking on both old and new browsers due to missing `typeArg` and/or unsupported `MouseEventConstructor`

From react-draggable

  • Bugfix: Fix return false to cancel onDrag breaking on both old and new browsers due to missing typeArg and/or unsupported MouseEventConstructor. Fixes #164.
View originalPermalink
How v2.1.2 went
v2.2.0

2.2.0

Added 1
  • offsetParent property for an arbitrary ancestor for offset calculations
Changed 1
  • Make this library iframe-aware
Fixed 1
  • Lint and test fixes for new Flow and React versions

From react-draggable

View originalPermalink
How v2.2.0 went
v2.1.0

2.1.0

Fixed 1
  • Fix improperly missed `handle` or `cancel` selectors if the event originates from a child of the handle or cancel

From react-draggable

  • Fix improperly missed handle or cancel selectors if the event originates from a child of the handle or cancel.
    • Fixes a longstanding issue, #88
    • This was pushed to a minor release as there may be edge cases (perhaps workarounds) where this changes behavior.
View originalPermalink
How v2.1.0 went
v2.1.1

2.1.1

Fixed 1
  • <DraggableCore> wasn't calling back with the DOM node

From react-draggable

  • Bugfix: <DraggableCore> wasn't calling back with the DOM node.
  • Internal: Rework test suite to use power-assert.
View originalPermalink
How v2.1.1 went
v2.0.1

2.0.1

Fixed 1
  • Fixed the IE10 constructor bug

From react-draggable

  • Finally fixed the IE10 constructor bug. Thanks @davidstubbs #158
View originalPermalink
How v2.0.1 went
v2.0.2

2.0.2

Fixed 2
  • Fix cannot access clientX of undefined on some touch-enabled platforms
  • Fixed a bug with multi-finger multitouch if more than 1 finger triggered an event at the same time

From react-draggable

  • Fix cannot access clientX of undefined on some touch-enabled platforms.
  • Fixed a bug with multi-finger multitouch if > 1 finger triggered an event at the same time.
View originalPermalink
How v2.0.2 went
v2.0.0

2.0.0

Changed 1
  • Event callbacks and position / defaultPosition API have changed
Fixed 2
  • Improved Flow 0.24 compatibility with small bugfixes
  • Stop assuming global.SVGElement exists, fixing JSDOM compatibility

From react-draggable

  • This is a breaking change. See the changes below in the beta releases.
    • Note the changes to event callbacks and position / defaultPosition.
  • Changes from 2.0.0-beta3:
    • Small bugfixes for Flow 0.24 compatibility.
    • Don't assume global.SVGElement. Fixes JSDOM & #123.
View originalPermalink
How v2.0.0 went
View all

Discussion

If you publish react-draggable, you can claim this product by proving you administer its repository.