Exit Button Closing Browser Windows

Sep 14, 2020

We have a very odd issue happening with certain users clicking the Exit button (close course) all of the browser windows close completely.  When the user returns they find out that they did not receive credit.  Course completion is triggered when the exit slide starts. 

This is happening in Chrome and only to certain users.  I originally thought it may be the Chrome version but through testing with different users using the same version, we could not replicate.

It is also interesting that when they relaunch the course and choose to resume from the prompt they are returned to a slide earlier in the  course where they must view 1 of 3 case studies before advancing.  AKA click 1 button before the next button is enabled.  

With these issues all playing against each other, the course for some users is a cycle that never gives credit.

Course is published HTML5/Flash, SCORM 1.2, hosted in LMS - SuccessFactors.


Any ideas on these?  And like I said, it is not happening to all users...

4 Replies
Leslie McKerchie

Hi Brad,

Thanks for reaching out and sharing what some of your learners are experiencing in the LMS.

  • Are you able to replicate the behavior with the same users? 
  • Have you taken a look in another environment, such as SCORM Cloud?

With your permission, I'd like you to share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.

Sungmin Hong

https://apps.support.sap.com/sap/support/knowledge/en/2876002

In nutshell,

Course progression data is stored with in popup window. it will only send it back to SF on closing of the window.  BUT Chromes new setting does not like went you stack "send 2 way msg" with "Exit" function so it will block it. 

 

It started with Chrome 80. 

https://community.articulate.com/discussions/articulate-storyline/chrome-80-update

 

Lauren Connelly

Hello Adam!

Can you share more information as to what you're running into? Are you finding this behavior occurs within an LMS or Web environment? Also, have you tested your course in multiple browsers?

It would be helpful if you can share your .story file too. You can attach it to this discussion or upload it privately in a support case.