Moodle

SCORM Activity Redirection wait

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Not a bug
  • Affects Version/s: 1.9.1, 1.9.2
  • Fix Version/s: None
  • Component/s: SCORM
  • Labels:
    None
  • Environment:
    Debian Linux, Apache
  • Database:
    MySQL
  • Affected Branches:
    MOODLE_19_STABLE

Description

Currently the following is displayed prior to loading each SCORM module:

You will be redirected to this activity in... 2 seconds
You will be redirected to this activity in... 1 seconds
You will be redirected to this activity in... 0 seconds
Activity loading, please wait...

There wasn't a 3-second wait before version 1.9.1, so why introduce it?

The singular of seconds should be used, i.e. "1 second"

Why show "0 seconds" at all? Surely redirect at that point?

I ask that this seemingly unnecessary load delay be removed, bypassed or explained.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dan Marsden added a comment -

Hi Peter,

the 3 second delay has been there for a long time(definitely pre 1.9.1) it's just that this wasn't communicated well to the user - it just showed a blank page until the SCORM loaded, and some users would refresh a few times causing other issues. - It just provides feedback to the user that it is loading and to be patient.

this delay is needed to allow all the api stuff to load correctly in all browsers before loading the scorm object. - without the delay, many scorm objects just won't play, as the browser hasn't loaded all it needs.

see MDL-14492 for more info on the timer thingy.

Show
Dan Marsden added a comment - Hi Peter, the 3 second delay has been there for a long time(definitely pre 1.9.1) it's just that this wasn't communicated well to the user - it just showed a blank page until the SCORM loaded, and some users would refresh a few times causing other issues. - It just provides feedback to the user that it is loading and to be patient. this delay is needed to allow all the api stuff to load correctly in all browsers before loading the scorm object. - without the delay, many scorm objects just won't play, as the browser hasn't loaded all it needs. see MDL-14492 for more info on the timer thingy.
Hide
Permalink
Peter Chamberlin added a comment -

Rather than a fixed timeout wouldn't it be better to make the SCORM instantiation dependent on the creation of the API object?

For example, API.php writes out "var API = new SCORMapi1_2();" near its final lines, so the SCO href change could be made then or on a window.setTimeout() callback. Thus a single line warning about load delay could be shown (easier to translate) and the wait time reduced to the bare minimum.

Alternatively a combination of window.onload events and a script load counter could be used to trigger the page transfer earlier from a higher point in the window chain once the necessary dependants have been loaded into the script host.

Particularly where there are multiple SCO assets within a package it gets quite tedious to wait for so long during content navigation, by which point the scripts are likely to have been cached in the browser session in any case.

Could you at least reduce the 3-second wait back to the 2-second one you had before? The JS code written by loadSCO.php could be adjusted to use the condition "if (cSeconds > 1)" instead of "if( cSeconds )"

Show
Peter Chamberlin added a comment - Rather than a fixed timeout wouldn't it be better to make the SCORM instantiation dependent on the creation of the API object? For example, API.php writes out "var API = new SCORMapi1_2();" near its final lines, so the SCO href change could be made then or on a window.setTimeout() callback. Thus a single line warning about load delay could be shown (easier to translate) and the wait time reduced to the bare minimum. Alternatively a combination of window.onload events and a script load counter could be used to trigger the page transfer earlier from a higher point in the window chain once the necessary dependants have been loaded into the script host. Particularly where there are multiple SCO assets within a package it gets quite tedious to wait for so long during content navigation, by which point the scripts are likely to have been cached in the browser session in any case. Could you at least reduce the 3-second wait back to the 2-second one you had before? The JS code written by loadSCO.php could be adjusted to use the condition "if (cSeconds > 1)" instead of "if( cSeconds )"
Hide
Permalink
Dan Marsden added a comment -

we couldn't just reduce the limit from 3 seconds to 2 as it just isn't enough for IE to ALWAYS work. - there were a range of issues in the tracker and in the forums related to this - increasing to 3 seconds has reduced the amount of tracker items and forum posts we've had to deal with!

but.... we could look at improving it to be more intelligent - feel free to submit a patch and we'll review it - otherwise we might look at this at a later date.

thanks,

Dan

Show
Dan Marsden added a comment - we couldn't just reduce the limit from 3 seconds to 2 as it just isn't enough for IE to ALWAYS work. - there were a range of issues in the tracker and in the forums related to this - increasing to 3 seconds has reduced the amount of tracker items and forum posts we've had to deal with! but.... we could look at improving it to be more intelligent - feel free to submit a patch and we'll review it - otherwise we might look at this at a later date. thanks, Dan

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.