Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-938 SCORM player
  3. MOBILE-1347

Intercept window.open inside the iframe to prevent make the app non-usable

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.8
    • Fix Version/s: 2.8
    • Component/s: SCORM add-on
    • Labels:
    • Testing Instructions:
      Hide
      1. Create a SCORM, IMSCP or Resource (iframe type) that uses window.open.
        • Please notice that, if the window.open is called right at the start, it should be placed inside a setTimeout.
      2. Open the activity in the app and check that the popup isn't opened, and an error message is shown instead.
      3. Check the same but using subiframes.
      Show
      Create a SCORM, IMSCP or Resource (iframe type) that uses window.open. Please notice that, if the window.open is called right at the start, it should be placed inside a setTimeout. Open the activity in the app and check that the popup isn't opened, and an error message is shown instead. Check the same but using subiframes.
    • Affected Branches:
      MOODLE_28_STABLE
    • Fixed Branches:
      MOODLE_28_STABLE

      Description

      We need to create a polyfill for window.open in the SCORM iframe, and recursively in all the nested iframes to prevent window.open function to be executed.

      We can just display a message like, your scorm uses some JavaScript functions not compatible or somethingote readable instead.

        Attachments

          Activity

            People

            Assignee:
            dpalou Dani Palou
            Reporter:
            jleyva Juan Leyva
            Peer reviewer:
            Juan Leyva Juan Leyva
            Integrator:
            Juan Leyva Juan Leyva
            Tester:
            Juan Leyva Juan Leyva
            Participants:
            Component watchers:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Fix Release Date:
              22/Jan/16