Exit or Close Button?

Hi Adam,

I can see where you're coming from, but on a mobile device, you don't see the tabs so it's not obvious or intuitive how to get back. You get to the end and then it's like cool now what, now I'm stuck.

A large proportion of our audience isn't IT savvy at all, so we have to ensure the UX is very intuitive.

I haven't played around with a window containing a course so I will look at that. Not sure how that affects the responsiveness. Also, it will reduce the screen real estate due to the padding of the moodle frame.

Thanks

Just another perspective on the rationale for this.  A lot of our users don't complete courses in a single pass, they need to be able to save their state and resume later (cmi.core.exit/cmi.exit == "suspend" + LMSFinish/Terminate).  It's not intuitive that closing a browser window will save state.  You wouldn't expect this if you were part way through an airline ticket purchase for example, why would you assume it for your eLearning?

For state to be saved reliably across LMS and be resumable, up until completion we would need a way to exit and set the exit status to "suspend" and after completion an exit button that exited normally.

Just lastly, please don't make the exit button close the window.  It's not the prerogative of the scorm activity to do this, the LMS chooses whether a scorm package is loaded in a new window and can close or navigate away accordingly when it receives a call to LMSFinish/Terminate.

Thanks in advance

Hi Adam,

We use e-learning modules inside moodle LMS. From a user's perspective, how do they get back to the LMS once they have finished the module? 

All our current modules have a close button that closes that window and then they are back to the course page.

Thanks

+1. I need this too. Our content opens in same window as LMS and the exit/finish command is needed to submit any data and then return the user to the LMS.

Cool. If we attach a close command to a button block, will that work for you folks?

Hi everyone, Just to highlight how critical a close button within the content actually is, here's a small test to show you how much can actually be achieved in an onbeforeunload handler.  The source code is linked to the page below, so feel free to download it and create your own test.  As you'll see Internet Explorer is the only browser that will give you near infinite time to execute requests when someone closes the browser.

http://www.andrewsmith.com.au/delay.html

While you might be finalising before the browser closes if the student completes the content, what about the scenario where someone wants to exit/bookmark and return?  Without a clear exit button within the content, the only way to do this is onunload or onbeforeunload.

The  time your browser will wait for whatever calls you make within these handlers varies per browser, but most only wait a very short period of time.  If you intend to set the session time, the score and the exit type for example in sequential requests (SCORM requires synchronous ajax), in a high latency environment, it's highly likely that 1 or all of these will fail.

So aside from the human side of this issue (be kind and let people know that they can safely save and exit) it simply isn't reasonable to expect that any synchronous ajax will complete during window close.

Andrew

Thanks Andrew for sharing that here - the test was a helpful demonstration. I've passed this along to our team in the form of a feature request so that it can be discussed internally. 

+1 for a close button. 

+1 for this

Traditionally I have not relied on close or exit buttons due to varying behaviours in different browsers... in some older IE browsers for example the exit simply does not work. Having said that an exit button would be useful, however should be tested across multiple browsers and versions.