Uploaded image for project: 'Opencast'
  1. MH-12523

"Submit" button in retract modal is always disabled

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed and reviewed
    • Affects versions: 4.0
    • Fix versions: 4.0
    • Labels:
      None
    • Severity:
      Incorrectly Functioning Without Workaround
    • Steps to reproduce:
      Hide
      Steps to reproduce:
      1. Start opencast locally, or with a fast backend so HTTP answers arrive fast.
      2. Create a new event, publish it somewhere (doesn't matter where).
      3. Click on "delete" in the events table for the corresponding event.
      4. The "retract" modal pops up. Its "Submit" button is disabled.
       
       Actual Results:
       
      The submit button is disabled, even after the list of workflows and publication channels has been successfully retrieved.
       
       Expected Results:
       
      The submit button might be disabled as long as the "get workflows" request is in flight, but afterwards, it's supposed to be enabled.
       
        Notes:

        I noticed that this doesn't happen with "slower" systems or if I manually throttle requests (for example, using the appropriate developer tool in chrome). I suspect this is a timing bug somewhere in `retractEventController.js` and/or `processing.js`.

      Show
      Steps to reproduce: 1. Start opencast locally, or with a fast backend so HTTP answers arrive fast. 2. Create a new event, publish it somewhere (doesn't matter where). 3. Click on "delete" in the events table for the corresponding event. 4. The "retract" modal pops up. Its "Submit" button is disabled.    Actual Results:   The submit button is disabled, even after the list of workflows and publication channels has been successfully retrieved.    Expected Results:   The submit button might be disabled as long as the "get workflows" request is in flight, but afterwards, it's supposed to be enabled.     Notes:   I noticed that this doesn't happen with "slower" systems or if I manually throttle requests (for example, using the appropriate developer tool in chrome). I suspect this is a timing bug somewhere in `retractEventController.js` and/or `processing.js`.

      TestRail: Results

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              middendorf Philipp Middendorf
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                TestRail: Cases