Storyline 3 spinning cursor when going through slides very fast

Jan 30, 2018

I have seen some posts on the "spinning cursor" problem.  We have this problem as well.  It generally manifests itself when we go through our slides very fast.  It happens in random places, but at some point, we get the spinning cursor, and we never recover.  It just keeps on spinning.  I don't have nested groups; some slides have animation, but it doesn't appear things are grouped together.

This happens most often on Safari; you don't even have to go as fast on Safari as other browsers, but it can happen on Chrome as well.  It never happens with the Flash version.  It does seem to be a loading problem, as the slower the network, the easier it is to get this to happen.  I realize that people shouldn't go super fast through slides, but I think this is a manifestation of a larger problem.  Has anyone else seen this, and is there a fix for this?  I have version 3.0.10762.0

Thanks

13 Replies
Todd Haynes

A course I've been developing has now experiencing several issues this week.

On my custom main menu slide, I get a spinning cursor issue and users cannnot select anything on the slide. The Hover States of the buttons are very inconsistent - some hover states don't appear, some appear after moving the cursor over the button several times. Some of the buttons users cannot click at all. In the slide, I removed any groups, animations, etc. If I remove everything but the 6 buttons, I still experience the issue. I deleted the buttons, and created new ones, and same issue came up.

Chris Smit

Hi there,

 

We seem to have the same problem. 

Ever since we have installed Update 3.3.15007.0 we are experiencing the loading cursor a lot. 

Just like Frank mentions it generally manifests itself when we go through our slides very fast, but actually it also happens a lot when we don't even click through but just let the slides follow up automatically. 

The loading cursor appears far more often (and in random places) then before, when we published our courses with a previous update. And, even more problematic courses get stuck completely. The loading cursor often never recovers and keeps on spinning. 

Is there any news on this issue or issues?! Is there a fix for this problem to be expected anytime soon?! And, for the time being, until there is a fix for it...is there a work-around that you know of?

 

Regards,

Chris

 

Chris Smit

Hi Alyssa,

 

We see this in our own LMS most of the time, but not exclusively. We even see it in the preview in certain situations.

I have also tested it in scorm cloud and find the same behaviour there.

What do you mean by your last question? Where we host it? We have a self built LMS.

The thing is, we didn't change anything there and these issues appeared (way more often) after updating to 3.3.15007.0.

 

 

Alyssa Gomez

Hi there Chris,

Thanks for sharing your files with our team! It looks like we've got a bug lurking here, specifically in the HTML5 output. We're seeing that the course becomes non-responsive after closing lightbox slide that jumps back to the originating slide.

As soon as we get this bug straightened out, we'll let you know. Thanks again for bringing this up to us, and I'm sorry if it's causing you headaches! 

Chris Smit

Hi Alyssa,

Thanks again for your reply. And even though it is giving me headaches, I am glad you guys are looking into it.

So, the lightbox part of the problem seems to be a bug.

Are you also still looking into the other part? The part where we are seeing more loading cursors (and even non-responsiveness) when we navigate/click through the course quickly?!

 

Kind regards,

Chris

Alyssa Gomez

Hi Chris,

Yes, our team is working on that one, as well! In summary, the two issues we're seeing in Storyline 3 are:

  1. A course becomes non-responsive after closing lightbox slide that jumps back to the originating slide in HTML5.
  2. Clicking quickly or rapidly causes a course to stall/freeze and results in a spinning loading cursor.

We've tagged this thread to be updated as soon as either of those bugs is fixed, so you'll be notified immediately. 

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