Drag and drop feedback malfunction

Sep 14, 2017

Some of my drag and drop slides are behaving strangely.

If you get the answer incorrect the first time you visit the slide, it will behave as normal.

If you get the answer right and get 'correct' feedback, then navigate away, then go back to that slide again (for example, redoing the quiz) you can drop the object anywhere on the page, and it will still give you positive feedback.

This is a standard 'drag and drop' template with one object, a hotspot target, and 'correct', 'incorrect' and 'try again' feedback slides.

Any suggestions?

12 Replies
Susi B

Hi Monica,

what are your slide properties? If you want to reset the slide when revisited, you should use slide advances by user and when revisiting reset to initial state. I would always use these two options as long as you don´t want them to see what their answers were and that they can retake the quiz. :)



Monica Hill

Hi Susi, thank you for your response. 

The slide properties are already slide advances by user, and when revisiting reset to initial state.

It isn't an issue of the answer remaining when they revisit the slide, but rather that once they have got the answer right, when they redo the quiz they won't ever get the 'incorrect' feedback even if they do something like drag the object onto the title or instruction rather than anywhere they would sensibly expect the answer might be. 

Hope that explains the issue a little better.

Monica Hill

Thank you! Sorry for the delay.
Here is a section of the module that has several examples of this issue.
First, you need to get the answer correct, then go back, try the question again but get it very obviously wrong, and you will see that it still gives you correct feedback.

Questions 1-6, and question 8 all have this issue.

I don't seem to have this issue with radio buttons, just drag and drop.

I thought it might be because I was using a hotspot rather than an invisible rectangle as the drop target (the drag and drop questions that are working fine do not use hotspots), but I changed that on question 1 and it didn't fix it. Then again, it might be a multi-level issue.

Thank you for taking a look at this.

Alyssa Gomez

Thanks for sending over the file, Monica. I did a bit of testing, and it appears that Freeform Drag and Drop interactions are marking answers incorrectly on the second attempt. We've got this bug reported to our team, and I'll make sure to add your experience to the report. I'll also tag this thread to be updated as soon as we find a fix. 

Until then, I would recommend using the setting "When Revisiting: Resume Saved State." With that setting, your learners will not be able to go back and change their answers on questions they've previously completed.

Thanks again for bringing this up, and I'm sorry it's causing such a headache for you!

Monica Hill

Thank you Alyssa, now I know how to temporarily fix up this issue. I'll be sure to pay close attention to make sure I don't miss a fix.

The strange thing is that it does not seem to affect all drag and drop types. It seems more likely to crop up if a hotspot is used as the drop target, but changing the drop target to an invisible rectangle doesn't seem to fix the issue.

If it would be helpful to see the whole file I could send it through, but straight to staff rather than through the forums if there is a way to do that (it is a very large file though).

Ashley Terwilliger-Pollard

Hi all,

Great news!  We just released another update for Articulate 360, and included a few important fixes and new features that you'll see in the release notes here.  

The item you'll be interested in is how it fixed the issue where freeform drag-and-drop questions could be marked correct on the second attempt in HTML5 output even when learners answered incorrectly.

Just launch the Articulate 360 desktop app on your computer and click the Update button for each application. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly. 

This discussion is closed. You can start a new discussion or contact Articulate Support.