Moodle

IE 8 in compatibility mode causes failure with SCORM scoring

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Not a bug
  • Affects Version/s: 1.9.12, 2.0
  • Fix Version/s: None
  • Component/s: SCORM
  • Labels:
  • Affected Branches:
    MOODLE_19_STABLE, MOODLE_20_STABLE

Description

When IE 8 is operating in compatibility mode scoring seems to fail - more info here:

http://moodle.org/mod/forum/discuss.php?d=182002#p793451

AFAIK There's no easy way for us to add meta tags to a page anymore unless we use $CFG->additionalhtmlhead which gets a bit hacky - and we should probably trace it further to find out why/where it is failing anyway.

Activity

Hide
Michael de Raadt added a comment -

Have you found any evidence of this on other pages?

Does the SCORM module use the $PAGE object like other page?

Show
Michael de Raadt added a comment - Have you found any evidence of this on other pages? Does the SCORM module use the $PAGE object like other page?
Hide
Dan Marsden added a comment -

yup - using $PAGE, but last time I checked (a while back) - you couldn't easily use $PAGE->requires() to add a meta tag to the header and there weren't any other functions that did this - has that been improved?

also - I haven't seen this occurring yet myself - just created the Tracker issue to make sure I take a look and see if I can see where/why it's failing.

Show
Dan Marsden added a comment - yup - using $PAGE, but last time I checked (a while back) - you couldn't easily use $PAGE->requires() to add a meta tag to the header and there weren't any other functions that did this - has that been improved? also - I haven't seen this occurring yet myself - just created the Tracker issue to make sure I take a look and see if I can see where/why it's failing.
Hide
Matteo Scaramuccia added a comment -

Hi Dan and Michael,
not sure about the fix, as already told by Dan.
Besides I guess that it could be more correct to use:

<!--[if IE]>
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
<![endif]-->

to allow Internet Explorer to use the highest mode available (http://msdn.microsoft.com/en-us/library/cc288325%28v=vs.85%29.aspx#SetMode) and not a specific one, IE=8 in the forum thread.
BTW, I'll try myself to replicate the issue using IE 8 in compatibility view.

Matteo

Show
Matteo Scaramuccia added a comment - Hi Dan and Michael, not sure about the fix, as already told by Dan. Besides I guess that it could be more correct to use:
<!--[if IE]>
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
<![endif]-->
to allow Internet Explorer to use the highest mode available (http://msdn.microsoft.com/en-us/library/cc288325%28v=vs.85%29.aspx#SetMode) and not a specific one, IE=8 in the forum thread. BTW, I'll try myself to replicate the issue using IE 8 in compatibility view. Matteo
Hide
Dan Marsden added a comment -

closing as "not a bug" - the reporter had previously customised the function "DoRequest" in request.js and had introduced the issue in their local installation.

Show
Dan Marsden added a comment - closing as "not a bug" - the reporter had previously customised the function "DoRequest" in request.js and had introduced the issue in their local installation.

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: