-
Bug
-
Resolution: Fixed
-
Major
-
3.6
-
MOODLE_36_STABLE
-
MOODLE_36_STABLE
-
MDL-63625-master -
This is a followup of MDL-51803, where some problems were detected in the testing phase. Borrowed from there:
michaelh added a comment -
PC Testing
Setup: Ubuntu using both Firefox and Chrome
This mostly all worked fine for desktop, both with mouse and keyboard, I just found an issue with example 7:
Example 7 - embedded lists: The way the JS works, means that if you click on the move handle of the child items (that fall within "sort activities", sort-example7b), it also triggers the code for "sort section", sort-example7a, which is the parent. The result is that two modals are loaded, one to move the item you've clicked, and another to move the whole section it resides within (which you will see once closing/choosing on the first modal).
While this might just be a bug in the way the test script is written, my main concern is that this could demonstrate a potential implementation issue if certain draggable sections reside within other draggable sections when used in production, having unintended side effects of triggering more move requests than intended, from some other JS block elsewhere in the code.
Mobile
Android:
No consistent issues specific to the latest Android, using Chrome.iOS:
Tested with the same results on both Safari and Chrome on the following setups:
iPhone 6 on IOS 11.2.5
iPhone 8 on IOS 12
- All lists using the move handle, apart from the first one (vertical list): After selecting move, and choosing an option, the modal is not closed. After manually closing using cancel or the cross icon, the move handles for the whole page no longer work, requiring a page refresh.
- Dragging is difficult and not intuitive to use in iOS, for two reasons:
- If you simply touch over the move handle and drag, it will scroll the page. It will only work after long press, which causes the cursor to highlight the text for the item you are moving, then you can move the items. See demo1 video.
- For draggable items with no move handle, it's capturing the touch on the item, but continuing to scroll the page (although highlighting the row, and also showing text as if dragging is going to happen). See demo2 video.
Thanks,
Mick