Nesting PathView and Flickable/Listview causes PathView to stop at wrong offset in some cases

When PathView and Flickable/ListView are nested, PathView stops at wrong offset in some cases. Please see the attached example code of the situation where the ListView is embedded in a PathView (the issue can also be reproduced the other way around - I've confirmed this with having a PathView inside a Flickable).

Step to reproduce is this:

1) Start to change the column in the example by dragging the view horizontally.
2) Quickly release the mouse while the PathView is moving between columns, and start to scroll the ListView vertically.
3) Release the mouse.

Expected is that the PathView completes the movement - but instead, it is left between two columns (in this case, the example code prints a "*** BUG" text to the console). The visible ListViews can be still scrolled, but just clicking (not dragging) triggers finally the correct behavior: the PathView scrolls to the closest item.