The module will have opened in a fresh browser window, this will be on the users own PC.
The server/LMS won't typically close the browser window, would you want a remote server to be able to access your running applications and be able to do things with them? For a staert it needs to access your PC to see what applications are running, it then needs to identify the specific instance that has the module open in it and then issue a command to close it. Allowing this kind of thing to happen raises very worrying security issues.
So the user should close the module or you add a little code to do this.
Just add an object that can be clicked on with some text that says something like 'close this module'
Add to this an 'on click' event with a javascript action.
Make the javascript code self.close()
Clicking your button object will now close down that specific instance of the browser.
Should work on all browsers.
You could also have it auto close on completion using the same snippet of javascript in a different way
The module will have opened in a fresh browser window, this will be on the users own PC.
The server/LMS won't typically close the browser window, would you want a remote server to be able to access your running applications and be able to do things with them? For a staert it needs to access your PC to see what applications are running, it then needs to identify the specific instance that has the module open in it and then issue a command to close it. Allowing this kind of thing to happen raises very worrying security issues.
So the user should close the module or you add a little code to do this.
Just add an object that can be clicked on with some text that says something like 'close this module'
Add to this an 'on click' event with a javascript action.
Make the javascript code self.close()
Clicking your button object will now close down that specific instance of the browser.
Should work on all browsers.
You could also have it auto close on completion using the same snippet of javascript in a different way
