onEnd() not called when item dropped to a different spot

[Blackbaud-JasonBodnar]

We've been using sortablejs (and ng-sortablejs) for several years without problem. Recently, when an item is dragged to a new position our onEnd callback is not getting called. If I start to drag the item but drop it in its current position onEnd is called.

We're using sortablejs-1.14.0 and ngx-sortablejs-3.1.4. (I tried ngx-sortablejs-11.1.0 but it didn't fix things.)

Our options look like:

{
    group: {
      name: 'sortable',
      put: true
    },
    handle: '.draggable-handle',
    animation: 300,
    onAdd: (event: any) => {
      this.addItem(event);
    },
    onUpdate: (event: any) => {
      this.updateItem(event);
    },
    /* tslint:disable:no-unused-expression */
    onStart: () => {
      document && this.renderer.addClass(document.body, 'dragging');
      console.log('*** starting and adding dragging class', document.body.className);
    },
    onEnd: () => {
      console.log('*** onEnd start');
      document && this.renderer.removeClass(document.body, 'dragging');
      console.log('*** ending and removing dragging class', document.body.className);
    }
    /* tslint:enable:no-unused-expression */
  }

Do I need to tinker with a threshold setting? Why would it suddenly stop working? I've tested on Chrome, FF and Opera.

After setting some breakpoints, it seems that Sortable.active is null when I move the item to another position. If I start to drag it but leave it in its existing position Sortable.active is defined. This preventing the end event from being sent:

if (Sortable.active) {
          /* jshint eqnull:true */
          if (newIndex == null || newIndex === -1) {
            newIndex = oldIndex;
            newDraggableIndex = oldDraggableIndex;
          }

          _dispatchEvent({
            sortable: this,
            name: 'end',
            toEl: parentEl,
            originalEvent: evt
          }); // Save sorting


          this.save();
        }

Why would this start happening?