courselab.js seems to break with IE11.
I tried version 2.4 and 2.7 with no luck.
Is there an updated courselab.js that can be downloaded that fixes the problem?

IE11 seems to come preconfigured to run in a state of total paranoia, that is most anything it sees especially active-x and javascript it will disable.
OPTION #1. The javascript isn't broken, 11 is just not using it, you need to change the browsers settings to allow the javascipt API to be used. This is quite likely to be happening.
OPTION #2. The main file that is interpreted into the pages of content isn't being run in the correct compatibility mode. This may be possibly what is happening

I've been trying to find an old post which covered this by declaring the DTD specifically so a specific interpretation of the data at the web engine was used.

11.12.2013 00:22 James Nick wrote:
IE11 seems to come preconfigured to run in a state of total paranoia, that is most anything it sees especially active-x and javascript it will disable.OPTION #1. The javascript isn't broken, 11 is just not using it, you need to change the browsers settings to allow the javascipt API to be used. This is quite likely to be happening.OPTION #2. The main file that is interpreted into the pages of content isn't being run in the correct compatibility mode. This may be possibly what is happeningI've been trying to find an old post which covered this by declaring the DTD specifically so a specific interpretation of the data at the web engine was used.

James

I have also had this problem and it appears that courselab will not run with IE11 when you publish it for a CD. I was able to make it run by manually changing IE to being IE10 compatible. Is this something that can be fixed whe3n publishing courselab or will there be a patch to courselab

Slav Shchinov of Courselabs development team has told me that there will be an update to 2.7 in the near future that will fix this problem.

What is happening is that the splash page has a header for the web page (meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7") that tells IE to use a version 7 compatibility mode.
What then happens is that the splash page works but the child page where the content is displayed doesn't inherit the compatibility instructions and fails. This shouldn't happen and is really a fail in IE

It is a constant battle to keep anything that is web based running consistently and sometimes even working as new versions of IE are released.

I'm wondering if the meta tag can be added into the content display page somewhere, this would be a manual task to be undertaken once the module/course was 'published'.
NICK

As an update to this IE11 problem.

The fix is basically simple and just needs one line of html added to the web code that launches the module.
This can be done using notepad on both standalone modules and the zip bundles for SCORM or AICC.
As far as I can test this it is a good clean fix.
Currently it is manual, that is you need to do it yourself though it might be possible to automate this which I am looking at particularly for 2.4 users as it is unlikelly this will be updated. 2.7 users should see an update to fix this.

I've got a PDF detailing this at http://www.friendsofcourselab.info/index.php/learn/

11.03.2014 02:01 James Nick wrote:
As an update to this IE11 problem.The fix is basically simple and just needs one line of html added to the web code that launches the module.This can be done using notepad on both standalone modules and the zip bundles for SCORM or AICC.As far as I can test this it is a good clean fix.Currently it is manual, that is you need to do it yourself though it might be possible to automate this which I am looking at particularly for 2.4 users as it is unlikelly this will be updated. 2.7 users should see an update to fix this.I've got a PDF detailing this at http://www.friendsofcourselab.info/index.php/learn/

I have tried your suggestion here, but it still does not work with IE 11. Do we know if 2.7 has been updated yet for IE11? Will 2.4 be updated to work with IE11?

Odd as it works for me both on this PC, and served off of an LMS.
2.7 should be in the next update as far as I know
2.4 is unlikely to e updated.

I'll retest in a few more enviroments and do an update on this.

22.03.2014 03:42 James Nick wrote:
Odd as it works for me both on this PC, and served off of an LMS.2.7 should be in the next update as far as I know2.4 is unlikely to e updated.I'll retest in a few more enviroments and do an update on this.

Ah, figured it out. You have to put your code directly after the open <head> tag like it is shown in your example. However your instructions say it just needs to be between the <head> and </head> tags. I put it right before the </head> tag. Once I moved it between the <head> and the <title></title> lines it worked fine. Thanks for the fix!

I wondered what was happening as it was working OK for me. It shouldn't matter really where it goes as long as it is between the head tags, having it first is going to be IE being very pedantic I guess.

I might just make a full replacement file as the page does very little.

22.03.2014 22:38 James Nick wrote:
I wondered what was happening as it was working OK for me. It shouldn't matter really where it goes as long as it is between the head tags, having it first is going to be IE being very pedantic I guess.I might just make a full replacement file as the page does very little.

I have added the code to all the start.html files from each module and it works when I open each file with IE11. But then, I zip the scorm folder, upload to moodle and when I try to open the scorm I get a white screen.
It's really annoying

Mora that is because the html is re-written when the module is published.
You can either:
#1 Open the scorm zip and edit the html file.
#2 Have a copy of the file already changed somewhere and copy that into the zipped folder to overwrite the original.
For unzipping files Winzip, winrar or 7zip are nice, of these 7zip is free but has as good a GUI and range of features ( http://www.7-zip.org/ ).

Remember if you make any fundamental changes to any of the code that runs courselab BEFORE you publish (to make something work or add some specific feature) THEN it will not be there after publishing.