Interesting, so there was a second, subtler bug affecting all list views on top of the o2m-specific one: this "new" issue apparently arose if an only if a row was dropped in its original position (a click which misfired into a drag for instance).
It should be fixed as well in trunk@rev <email address hidden>
Interesting, so there was a second, subtler bug affecting all list views on top of the o2m-specific one: this "new" issue apparently arose if an only if a row was dropped in its original position (a click which misfired into a drag for instance).
It should be fixed as well in trunk@rev <email address hidden>