Drag and Drop Breaks on Second Visit
Dec 13, 2023
By
Digital Lab
Hi, everyone,
I created a single slide drag-and-drop activity, where users sort some statements into two groups. The slide is set to 'reset to initial state', so when the user revisits the slide, they can redo the activity.
Everything worked fine in preview until it was uploaded to an LMS. The activity works fine when opened for the first time, but when it is revisited, drag becomes sticky and user has to click again to drop the item. All drop zones are also displaced. Not sure if this is a bug or my error. Any help would be appreciated. Thanks.
5 Replies
Thanks for sharing the file.
I think I would probably disable or delete these triggers. The reset in the Properties is going to take care of these state changes. I also noticed the Slide properties were set to automatically advance, but with a pause timeline trigger. I am not sure if I understand the intention of those two controls.
Hi, Ron. Thanks for looking into the issue. I added these dummy triggers after discovering the bug to test if each element is reset and behaving correctly upon revisit. The bug still persists after the triggers are removed. (Please see attached)
Three mysteries that is perplexing to me:
1. Why the activity works the first time but not the second time
2. Upon the second time, a single mouse click will pick up the item, and another click will drop it down, as opposed to the original drag-and-release behavior
3. The drop zone appeared to have been displaced the second time as shown in the picture attached.
Any idea why?
Thanks.
I have not been able to replicate any issues using your file. Is this only happening in the LMS?
It is in LMS and only when the activity is visited the second time.
I have figured out why.
In my player setting, the resume setting is set to: 'on restart - always resume'. So when the activity is revisited, although everything is reset to their initial position on the slide, objects still inherited their states from previous sessions, so the drop items don't quite if they are correct or not...
I changed the resume setting to 'on restart - never resume'. Now, the module completely resets and everything is normal again.
Great catch. Glad you found the solution.