I have found that the EXIT tab does not behave as it should when using Safari on an iPad device running from an LMS. EXIT causes Safari to close down completely. This is a totally solid fault. Chrome doesn't have the same problem.
Given there are a lot of Safari users out there - does anyone have a workaround for this?
There may be a couple of reasons for this, but I'm not able to reproduce this on my end.
I published a very quick project for HTML5, uploaded to Articulate Online and opened the URL directly in Mobile Safari. Clicking on the "Exit" tab will close the window that houses the content, but if you have other content open, that content doesn't close.
For example, if you have content open in one tab for the LMS and then launch the course in a new tab, the LMS tab will still be open when you close the course - or at least, it should be :)
Can you tell us a little more about the LMS you're using and how the content is launching in Safari? If it's launching in the same tab as the course, that may be why the entire browser is closing.
If that's not the case, what iOS, Safari version, and device (iPad, iPad2, iPad Mini) are you using to test the project?
Hi Christine - thanks for your reply. You are right to say that the EXIT button wont close other pages that are open - but it does consistently kill the browser page you have open to run the content. The test project you created does the same thing on my iPad.
It is of little benefit that other pages remain open when the browser page is terminated because it will still kick a user out of their LMS session. By contrast, Google Chrome exits cleanly and returns the user to the relevant entry page on the LMS - rather than terminating their whole session.
You are also right to suggest that setting up the course to open in a new TAB it is a potential workaround to the problem. However that just introduces a whole new set of problems with pop up blockers etc.
Hopefully some fix will be introduced to make Presenter based content viewed on Safari behave in the same way it does when viewed on other browsers. Ideally the HTML5 versions will behave consistently with the Flash based versions - but this is not the case as yet. The EXIT issue is an inconsistency that is a little harder to work around than other issues I have encountered so far.
I know this thread is a little old, but I am having the same issue described. I updated to the latest Storyline build, and have the latest iOS. Safari closes down the LMS session when the exit course button is clicked. It works correctly in our LMS (moodle).
I am using Storyline 2, and it appears to do the same thing in Tempshare, but it's hard to say since the exit course button just closes the browser window there. We just had the course open a new browser window, so Exit Course shuts down that window and drops you back on the course page in the LMS. The grade is reported in this scenario, so for now we will have a standard version and a mobile version of our courses. Our tech people want the course to run on the LMS page, and not in a pop-up when possible.
Thanks for the details Philip and glad you have a temporary solution. Could you share your .story file with our team here so that we can take a look and further investigate.
6 Replies
Hi Phil,
There may be a couple of reasons for this, but I'm not able to reproduce this on my end.
I published a very quick project for HTML5, uploaded to Articulate Online and opened the URL directly in Mobile Safari. Clicking on the "Exit" tab will close the window that houses the content, but if you have other content open, that content doesn't close.
For example, if you have content open in one tab for the LMS and then launch the course in a new tab, the LMS tab will still be open when you close the course - or at least, it should be :)
Here's the project I used for testing:
http://chendrickson.articulate-online.com/4556513325
Can you tell us a little more about the LMS you're using and how the content is launching in Safari? If it's launching in the same tab as the course, that may be why the entire browser is closing.
If that's not the case, what iOS, Safari version, and device (iPad, iPad2, iPad Mini) are you using to test the project?
Thanks!
Hi Christine - thanks for your reply. You are right to say that the EXIT button wont close other pages that are open - but it does consistently kill the browser page you have open to run the content. The test project you created does the same thing on my iPad.
It is of little benefit that other pages remain open when the browser page is terminated because it will still kick a user out of their LMS session. By contrast, Google Chrome exits cleanly and returns the user to the relevant entry page on the LMS - rather than terminating their whole session.
You are also right to suggest that setting up the course to open in a new TAB it is a potential workaround to the problem. However that just introduces a whole new set of problems with pop up blockers etc.
Hopefully some fix will be introduced to make Presenter based content viewed on Safari behave in the same way it does when viewed on other browsers. Ideally the HTML5 versions will behave consistently with the Flash based versions - but this is not the case as yet. The EXIT issue is an inconsistency that is a little harder to work around than other issues I have encountered so far.
I know this thread is a little old, but I am having the same issue described. I updated to the latest Storyline build, and have the latest iOS. Safari closes down the LMS session when the exit course button is clicked. It works correctly in our LMS (moodle).
Hi Philip!
I do see a possible similar issue. Are you utilizing Storyline 1? Are you able to reproduce this issue in SCORM Cloud or is it limited to your LMS?
This issue looks to be in the hands of our QA Team.
I am using Storyline 2, and it appears to do the same thing in Tempshare, but it's hard to say since the exit course button just closes the browser window there. We just had the course open a new browser window, so Exit Course shuts down that window and drops you back on the course page in the LMS. The grade is reported in this scenario, so for now we will have a standard version and a mobile version of our courses. Our tech people want the course to run on the LMS page, and not in a pop-up when possible.
Thanks for the details Philip and glad you have a temporary solution. Could you share your .story file with our team here so that we can take a look and further investigate.
This discussion is closed. You can start a new discussion or contact Articulate Support.