Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-42245 META: Follow up issues with new course management interface
  3. MDL-42299

Resorting categories closes expanded nodes

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.6
    • 2.6
    • Course
    • MOODLE_26_STABLE
    • MOODLE_26_STABLE
    • 42299-26
    • Hide
      1. Log in as an admin.
      2. Browse to course category management interface.
      3. Expand some categories by clicking the plus icon next to them.
      4. Refresh the page (F5).
      5. Check that the categories you had expanded are still expanded.
      6. Close some of the categories by clicking the minus icon next to them.
      7. Refresh the page (F5).
      8. Check that the categories you had expanded are still expanded, and the ones you closed are still clsoed.
      9. Run the behat test suite (it tests the above as well)
      Show
      Log in as an admin. Browse to course category management interface. Expand some categories by clicking the plus icon next to them. Refresh the page (F5). Check that the categories you had expanded are still expanded. Close some of the categories by clicking the minus icon next to them. Refresh the page (F5). Check that the categories you had expanded are still expanded, and the ones you closed are still clsoed. Run the behat test suite (it tests the above as well)

      Reported by Ankit on MDL-31830: "When am clicking on Re-sort subcategories all expanded nodes are closed when the page reloads"

            samhemelryk Sam Hemelryk
            damyon Damyon Wiese
            Eloy Lafuente (stronk7) Eloy Lafuente (stronk7)
            Dan Poltawski Dan Poltawski
            Andrew Lyons Andrew Lyons
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.