Sorry Mc but that wasn't clear in the question you'd posted (it was an interesting experiment I did though )but......
The 'rules' for SCORM 1.2 and 2004 do as far as I remember (without wading through a pile of reading to confirm) say that resources used by a module should be packaged as a part of the module itself and references to the resources made relative to the module root.
So really reference to external URLs or files aren't strictly allowed if your being standards conformant. The reasoning for this being if it's important enough to include in the module then it's important not to leave it to chance that (a) the viewer has internet access and (b)the resource hasn't been moved, deleted or depracated. In either case your module is broken and a an element is missing from it.
This external referencing will most probably be addressed in the SCORM 2.0 version release which is due out next year and is a major revision rather than an evolution. However IMHO using a resource that might no longer be accessible as a part of a module can't be consider either sensible or sound and should be avoided if at all possible.
So IE is following the SCORM 'rules' and Firefox isn't although I suspect its quite by accident rather than by design in firefoxs case.
IE is probably behaving like this as the page is launched from an hta, this to IE makes it (your module) a trusted source so it largely does what it's told to by disabling the usual security model within IE. It also means any scripts are rigorously applied, in this case the Courselab SCORM runtime API.
This is also the reason why your javascript call for an external url does work without raising alerts from IE ,no pop up warnings, the security settings are totally off.
Firefox is either being a little more intelligent or negligent depending on your viepoint in the way it is interpreting this call to an external url.
WORKAROUND (?): Off the top of my head without testing the best I can suggest is... If you go into the published files the folder named 1 contains a file called runtime.
Open with something like notepad and use find and search for http:// you should find your external reference.
Check it's http://ww.thesite.com/object and correct it if it's wrong or changed. The http reference will be wrapped in quotes or brackets.
DON'T change anything else!!
Sorry Mc but that wasn't clear in the question you'd posted (it was an interesting experiment I did though )but......
The 'rules' for SCORM 1.2 and 2004 do as far as I remember (without wading through a pile of reading to confirm) say that resources used by a module should be packaged as a part of the module itself and references to the resources made relative to the module root.
So really reference to external URLs or files aren't strictly allowed if your being standards conformant. The reasoning for this being if it's important enough to include in the module then it's important not to leave it to chance that (a) the viewer has internet access and (b)the resource hasn't been moved, deleted or depracated. In either case your module is broken and a an element is missing from it.
This external referencing will most probably be addressed in the SCORM 2.0 version release which is due out next year and is a major revision rather than an evolution. However IMHO using a resource that might no longer be accessible as a part of a module can't be consider either sensible or sound and should be avoided if at all possible.
So IE is following the SCORM 'rules' and Firefox isn't although I suspect its quite by accident rather than by design in firefoxs case.
IE is probably behaving like this as the page is launched from an hta, this to IE makes it (your module) a trusted source so it largely does what it's told to by disabling the usual security model within IE. It also means any scripts are rigorously applied, in this case the Courselab SCORM runtime API.
This is also the reason why your javascript call for an external url does work without raising alerts from IE ,no pop up warnings, the security settings are totally off.
Firefox is either being a little more intelligent or negligent depending on your viepoint in the way it is interpreting this call to an external url.
WORKAROUND (?): Off the top of my head without testing the best I can suggest is... If you go into the published files the folder named 1 contains a file called runtime.
Open with something like notepad and use find and search for http:// you should find your external reference.
Check it's http://ww.thesite.com/object and correct it if it's wrong or changed. The http reference will be wrapped in quotes or brackets.
DON'T change anything else!!
