I got a report today that a Storyline 360 drag-and-drop activity (HTML5) was not registering correct answers. This was from someone using Google Chrome 64 on a Mac. I was able to reproduce this error in version 64 but not version 63, so it sounds like something in the most recent Chrome update broke this.
I republished and the problem went away! I went and looked at the version history for Storyline 360, and sure enough, issues with drag-and-drop were fixed in the most recent 2 releases. So, moral of the story is that if you have courses that use drag-and-drop activities and they were working, you might want to go check on them. They may need to be republished and replaced.
I agree. There must have been major change(s) to Chrome in version 64. I’ve noticed several posts here where people are experiencing problems with this new version of Chrome and HTML5. I’d love it if anyone who knows what changed would be willing to explain. It’s discouraging to think that maybe we should have stuck with Flash a bit longer.
I wonder if updating to Chrome 65 (current developer version) would make a difference in seeing whether what was broken in 64 was fixed in 65. I'm doubtful, but it might be worth a try. (Depending on whether this is a Chrome bug or something Google changed intentionally).
I'm also checking to see if the drag and drop hotspots on our interactions are shapes with no fill or filled shapes with 99% transparency. Sometimes interactions don't play nicely with no-fill shapes, and I can't recall how we approached the design on these. Regardless, the fact that these work on Firefox and Edge indicate a Chrome-specific interpretation issue for now.
In Storyline 360, we were seeing an issue in HTML5 where the Submit button was completely unresponsive. Since then, we've released a fix for that issue in the latest update.
You mentioned you're seeing this problem in Storyline 3. I just tested a Storyline 3 drag and drop interaction in Chrome, and I was able to use the Submit button without an issue.
Do you have a sample file you wouldn't mind sharing with me? I'm curious if the problem you're seeing is related to the Storyline 360 bug, or if it's something else entirely.
Was this an issue prior to version 64 of Chrome? Or did the update to Chrome cause the issue to start occurring? If it was due to the Chrome update, I think it would be useful in the release notes to indicate this here and for any future issues. Something like, “For users who had updated to Chrome 64, there was an issue with states that could cause some features to fail in HTML5 output.”
I should clarify here: the interaction we built isn't using drag-and-drop freeform or graded interaction slides, it uses object triggers.
These interactions auto-advance when complete because they feature one object to one drop spot per exercise. We were using custom shapes to define the hotspots but we were able to work around the Chrome issue by using the built-in hotspot feature instead.
Yes, we started seeing the issue with Chrome v.64. The Storyline 360 update we released on February 1 included a fix for that issue, as well as other bugs that weren't related to Chrome v.64. But I will certainly pass along your feedback because I can understand how that information would be helpful to our customers.
Hey Sam,
Ah, thanks for clarifying! It sounds like the problem you're seeing in your file isn't related to the bug I mentioned earlier. I'm happy to hear you found a workaround, though. If you'd still like a second pair of eyes on your file, you can alway send it along to us here for testing!
11 Replies
Do you know if this problems happens also with SL3?
We're having the same issue in Storyline 3. We think it's got to do with the recent Chrome update. This issue occurs on PC for us.
This post was removed by the author
I agree. There must have been major change(s) to Chrome in version 64. I’ve noticed several posts here where people are experiencing problems with this new version of Chrome and HTML5. I’d love it if anyone who knows what changed would be willing to explain. It’s discouraging to think that maybe we should have stuck with Flash a bit longer.
It's seems that only IOS is the only one that is not affected, for me is the only Device that didn't break my activities
I wonder if updating to Chrome 65 (current developer version) would make a difference in seeing whether what was broken in 64 was fixed in 65. I'm doubtful, but it might be worth a try. (Depending on whether this is a Chrome bug or something Google changed intentionally).
I'm also checking to see if the drag and drop hotspots on our interactions are shapes with no fill or filled shapes with 99% transparency. Sometimes interactions don't play nicely with no-fill shapes, and I can't recall how we approached the design on these. Regardless, the fact that these work on Firefox and Edge indicate a Chrome-specific interpretation issue for now.
iOS browsers are all really using the same engine under the hood.
Hey Sam,
In Storyline 360, we were seeing an issue in HTML5 where the Submit button was completely unresponsive. Since then, we've released a fix for that issue in the latest update.
You mentioned you're seeing this problem in Storyline 3. I just tested a Storyline 3 drag and drop interaction in Chrome, and I was able to use the Submit button without an issue.
Do you have a sample file you wouldn't mind sharing with me? I'm curious if the problem you're seeing is related to the Storyline 360 bug, or if it's something else entirely.
You can attach your file right here. Thanks!
Hi Alyssa,
Was this an issue prior to version 64 of Chrome? Or did the update to Chrome cause the issue to start occurring? If it was due to the Chrome update, I think it would be useful in the release notes to indicate this here and for any future issues. Something like, “For users who had updated to Chrome 64, there was an issue with states that could cause some features to fail in HTML5 output.”
That would help us test our existing content.
Thanks,
Will
Hi Alyssa,
I should clarify here: the interaction we built isn't using drag-and-drop freeform or graded interaction slides, it uses object triggers.
These interactions auto-advance when complete because they feature one object to one drop spot per exercise. We were using custom shapes to define the hotspots but we were able to work around the Chrome issue by using the built-in hotspot feature instead.
Hi Will,
Yes, we started seeing the issue with Chrome v.64. The Storyline 360 update we released on February 1 included a fix for that issue, as well as other bugs that weren't related to Chrome v.64. But I will certainly pass along your feedback because I can understand how that information would be helpful to our customers.
Hey Sam,
Ah, thanks for clarifying! It sounds like the problem you're seeing in your file isn't related to the bug I mentioned earlier. I'm happy to hear you found a workaround, though. If you'd still like a second pair of eyes on your file, you can alway send it along to us here for testing!
This discussion is closed. You can start a new discussion or contact Articulate Support.