|
1 | 1 | # Changelog |
2 | 2 |
|
| 3 | +### 4.4.4 (July 4, 2021) |
| 4 | + |
| 5 | +- Add `preventDefault` prop to allow touch scroll |
| 6 | + |
3 | 7 | ### 4.4.3 (June 8, 2020) |
4 | 8 |
|
5 | 9 | - Add `nodeRef` to TypeScript definitions |
|
41 | 45 | `nodeRef` is also available on `<DraggableCore>`. |
42 | 46 | - Remove "browser" field in "package.json": |
43 | 47 | - There is nothing special in the browser build that is actually practical |
44 | | - for modern use. The "browser" field, as defined in |
| 48 | + for modern use. The "browser" field, as defined in |
45 | 49 | https://github.com/defunctzombie/package-browser-field-spec#overview, |
46 | 50 | indicates that you should use it if you are directly accessing globals, |
47 | 51 | using browser-specific features, dom manipulation, etc. |
48 | | - |
| 52 | + |
49 | 53 | React components like react-draggable are built to do minimal raw |
50 | 54 | DOM manipulation, and to always gate this behind conditionals to ensure |
51 | 55 | that server-side rendering still works. We don't make any changes |
52 | 56 | to any of that for the "browser" build, so it's entirely redundant. |
53 | | - |
| 57 | + |
54 | 58 | This should also fix the "Super expression must either be null or |
55 | 59 | a function" error (#472) that some users have experienced with particular |
56 | 60 | bundler configurations. |
|
61 | 65 | - The browser build will likely be removed entirely in 5.0. |
62 | 66 | - Fix: Make `bounds` optional in TypeScript [#473](https://github.com/strml/react-draggable/pull/473) |
63 | 67 |
|
64 | | -### 4.3.1 (Apr 11, 2020) |
| 68 | +### 4.3.1 (Apr 11, 2020) |
65 | 69 |
|
66 | 70 | > This is a bugfix release. |
67 | 71 |
|
|
72 | 76 | return React.cloneElement(this.props.children, {style: this.props.children.props.style}); |
73 | 77 | ``` |
74 | 78 | , `style` ends up undefined. |
75 | | -- Fixed a bug that caused debug output to show up in the build. |
| 79 | +- Fixed a bug that caused debug output to show up in the build. |
76 | 80 | - `babel-loader` cache does not invalidate when it should. I had modified webpack.config.js in the last version but it reused stale cache. |
77 | 81 |
|
78 | 82 | ### 4.3.0 (Apr 10, 2020) |
|
82 | 86 | - Thanks @schnerd, [#450](https://github.com/mzabriskie/react-draggable/pull/450) |
83 | 87 | - Fix an issue where the insides of a `<Draggable>` were not scrollable on touch devices due to the outer container having `touch-action: none`. |
84 | 88 | - This was a long-standing hack for mobile devices. Without it, the page will scroll while you drag the element. |
85 | | - - The new solution will simply cancel the touch event `e.preventDefault()`. However, due to changes in Chrome >= 56, this is only possible on |
| 89 | + - The new solution will simply cancel the touch event `e.preventDefault()`. However, due to changes in Chrome >= 56, this is only possible on |
86 | 90 | non-passive event handlers. To fix this, we now add/remove the touchEvent on lifecycle events rather than using React's event system. |
87 | 91 | - [#465](https://github.com/mzabriskie/react-draggable/pull/465) |
88 | 92 | - Upgrade devDeps and fix security warnings. None of them actually applied to this module. |
|
106 | 110 | * **`"module"`**: ES6-compatible build using import/export. |
107 | 111 |
|
108 | 112 | This should fix issues like https://github.com/STRML/react-resizable/issues/113 while allowing modern bundlers to consume esm modules in the future. |
109 | | - |
| 113 | + |
110 | 114 | No compatibility changes are expected. |
111 | 115 |
|
112 | 116 | ### 4.0.3 (Sep 10, 2019) |
|
0 commit comments