Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.6
    • Fix Version/s: 2.6
    • Component/s: SCORM
    • Labels:
    • Testing Instructions:
      Hide
      1. Enter a SCORM as a student and make sure no new JS errors occur (ignore any JS errors that previously existed) from the YUI3 code
      2. Test the new settings that are added -
        • scorm/nav - Module level setting - Controls wether the SCORM navigation panel is disabled, under content or floating.
          • No - when set to 'No' the navigation panel should not be displayed.
          • Under content - when set to 'Under content' the navigation panel should be displayed below the SCORM content in the center.
          • Floating - when set to 'Floating' the navigation panel should appear at position specified by the settings - scorm/navpositionleft and scorm/navpositiontop. The navigation panel when set to floating can be dragged around anywhere in the window.
            • scorm/navpositionleft and scorm/navpositiontop should be disabled when scorm/nav is not set to 'Floating'.
        • scorm/collapsetocwinsize - Site level setting - set a value and enter a SCORM package.
          • Reduce the size (width) of the browser window and notice the TOC should collapse automatically below the corresponding window size value.
          • Increase the width of window and the TOC should re-appear.
      3. TOC toggle button - It should appear next to title of the SCORM package. On pressing the toggle button in state < - will collapse the TOC. When pressed in state > - will expand the TOC.
        • When the TOC is forced collapsed by pressing the toggle button the TOC should not re-appear on increasing/decreasing the width of the browser window.
        • Once TOC is un-collapsed by pressing the TOC toggle button >, the TOC should again collapse when the window size is reduced below scorm/collapsetocwinsize value.
        • When TOC is disabled the TOC toggle button should not be visible.
      4. Responsive - The TOC and content should adjust to the available window size (width). The TOC will be in collapsed state by default on small screen devices like iPads and mobile phones, if scorm/collapsetocwinsize is appropriately set.
      5. TOC Tree - The TOC should be correctly rendered with YUI3 sm-treeview.
        • Any clickable nodes of the tree should navigate to the corresponding content.
        • The active content item should be highlighted in the TOC tree, also while navigating with navigation buttons.
        • TOC can be resized as before.
      6. Navigation buttons - the Next/previous navigation buttons should be enabled/disabled when content can/cannot be navigated forward/backward respectively.
      7. Content should not be trimmed at the bottom - specially on iOS devices (Safari) and should be scrollable with touch gestures.
      8. Upgrading - while upgrading the new scorm/nav setting should replace the scorm/hidenav setting and the corresponding value should be set for scorm/nav.
      Show
      Enter a SCORM as a student and make sure no new JS errors occur (ignore any JS errors that previously existed) from the YUI3 code Test the new settings that are added - scorm/nav - Module level setting - Controls wether the SCORM navigation panel is disabled, under content or floating. No - when set to 'No' the navigation panel should not be displayed. Under content - when set to 'Under content' the navigation panel should be displayed below the SCORM content in the center. Floating - when set to 'Floating' the navigation panel should appear at position specified by the settings - scorm/navpositionleft and scorm/navpositiontop . The navigation panel when set to floating can be dragged around anywhere in the window. scorm/navpositionleft and scorm/navpositiontop should be disabled when scorm/nav is not set to 'Floating'. scorm/collapsetocwinsize - Site level setting - set a value and enter a SCORM package. Reduce the size (width) of the browser window and notice the TOC should collapse automatically below the corresponding window size value. Increase the width of window and the TOC should re-appear. TOC toggle button - It should appear next to title of the SCORM package. On pressing the toggle button in state < - will collapse the TOC. When pressed in state > - will expand the TOC. When the TOC is forced collapsed by pressing the toggle button the TOC should not re-appear on increasing/decreasing the width of the browser window. Once TOC is un-collapsed by pressing the TOC toggle button > , the TOC should again collapse when the window size is reduced below scorm/collapsetocwinsize value. When TOC is disabled the TOC toggle button should not be visible. Responsive - The TOC and content should adjust to the available window size (width). The TOC will be in collapsed state by default on small screen devices like iPads and mobile phones, if scorm/collapsetocwinsize is appropriately set. TOC Tree - The TOC should be correctly rendered with YUI3 sm-treeview. Any clickable nodes of the tree should navigate to the corresponding content. The active content item should be highlighted in the TOC tree, also while navigating with navigation buttons. TOC can be resized as before. Navigation buttons - the Next/previous navigation buttons should be enabled/disabled when content can/cannot be navigated forward/backward respectively. Content should not be trimmed at the bottom - specially on iOS devices (Safari) and should be scrollable with touch gestures. Upgrading - while upgrading the new scorm/nav setting should replace the scorm/hidenav setting and the corresponding value should be set for scorm/nav .
    • Affected Branches:
      MOODLE_26_STABLE
    • Fixed Branches:
      MOODLE_26_STABLE
    • Pull Master Branch:
      master_MDL-39910

      Description

      GSOC 2013 project
      The SCORM player currently uses YUI2 code - it should be converted to YUI3 and we should add an HTML5 version of the player that can be used as a replacement for compatible browsers - especially to improve display on mobile devices.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Votes:
                  3 Vote for this issue
                  Watchers:
                  14 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    18/Nov/13