- Fix #36: Add null checks on
_currentDrag
.
- Migrate to null safety.
- Remove unnecessary new keyword.
- Fix #30: Cannot initialize Dropzone with List.
- Follow more code style conventions.
- Update dependencies.
- Add an option
minDragStartDistance
onDraggable
to define the minimum distance in pixels that is needed for a drag to start (#26). Default is4
pixels. This allows for clicks with tiny movement. The optionclickSuppression
has been marked as DEPRECATED as it had the same goal but a misleading name.
- Align dart version to support Dart 2 (#25).
- Support for creating a Draggable with
List<Element>
(in addition toElementList
andElement
).
- Remove cursor files. Support for
grab
,-webkit-grab
,grabbing
, and-webkit-grabbing
is good enough.
- Migrate to Dart 2.
- Since Chrome 56 touch event listeners are treated as passive by default. This disables the possibility to call
preventDefault
on an element which we must do to tell the browser not to scroll while dragging. To fix this in Chrome we set thetouch-action
css property. With this Chrome will not scroll (none
) or only scroll in one direction (pan-y
orpan-x
).
- Fix strong mode errors (#20).
- Fix bug: Provide reasonable fallback for event target when mouse position exits viewport (#19).
- Handle the edge case where destroy is called while dragging an avatar (#17).
- Fix strong-mode type errors (#15).
- Remove Shadow DOM example and (dev)dependency on Polymer (was causing some confusion).
- Allow a configurable clickSuppression distance (#13). We found that the click suppression was a little too aggressive for users with less mousing accuracy. They would attempt to click and trigger a small drag. Which then suppressed the click event and prevented the action they intended to complete.
- Remove null-aware operator since drone.io uses an old version of Dart that doesn't support this yet.
- Support for programmatic drag abort (see issue #11).
- BREAKING CHANGE: Refactoring the
AvatarHandler
. Only if you've implemented a customAvatarHandler
you might need to do some changes:setPointerEventsNone
andresetPointerEvents
were removed and don't need to be called any more. Pointer event styles are handled automatically.
- Fix
AvatarHandler
margin caching: TheAvatarHandler
only cached the margins once for everyDraggable
. This caused problems when margins of elements in the sameDraggable
had different margins or the margins were changed. Now the margins are reset after every drag.
- Fix #9: Using transformers in the main
pubspec.yaml
caused problems with projects depending on thednd
package.
- Fix #3: Shadow DOM is now supported. A
dnd-retarget
attribute must be added to all custom elements where events should be forwarded to the Shadow DOM children. - Fix #7: Add a css class (
dnd-invalid
by default) to dropzones when a not-accepted draggable is dragged over.
- Add a sortable example.
- Change comments according to new Dart Style Guide rule
(
///
instead of/** */
). - Move event dispatching calls from EventManager to Draggable (refactoring).
- Fix #4: Problem when an ancestor of the dragged element was positioned (relative, absolute, fixed).
- Correcting small bug that occurred when setSelectionRange() was called on an element that does not support it.
- Fix Pointer Event bug: Too many event listeners in move, end, cancel.
- Fix for Bug #1 - Not working in Windows 8.1 IE11
- Adding a
cancelled
flag toDraggableEvent
to indicate if a drag ended because of a cancelling operation likeesc
key, etc.
- Support for IE10 and IE11 touch screens through pointer events.
- Removed
disableTouch
anddisableMouse
options. The goal was to unify touch and mouse dragging, so it should not be necessary to disable one or the other.
- First version.