Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-4402

When using IE, the incident report screen's "close" button behaves just like its "submit" button

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.1.1
    • Fix Version/s: 1.0.3
    • Labels:
      None
    • Similar issues:
      KULRICE-11299Error when submitting incident report form
      KULRICE-4609Close/Cancel/Save button does not work correctly for Kim maintenance screens
      KULRICE-9214Incident Report page Cancel Button
      KULRICE-10003Close button on popover form does not work in IE
      KULRICE-9430Lightboxes, close and cancel buttons not working as expected
      KULRICE-9828Infinite reload on back button click for lookups in IE
      KULRICE-9464On submit of Send Adhoc button goes to incident report in Maintenance Document
      KULRICE-8617Delete button is not disabled when a proposition is added like the other buttons; works correctly in Internet Explorer.
      KULRICE-9444Weirdness with Incident Report Controller Code
    • Rice Team:
      QA

      Description

      For certain browsers like IE, clicking an incident report's "close" button is functionally equivalent to clicking its "submit" button, even if the exception that triggered the incident report explicitly hides the "submit" button and stack trace. (Firefox does not have this problem, though.) It appears that the incident report's related form and action classes only check for a "cancel" request parameter corresponding to the one generated by the "close" button, but they do not check for the existence of the button's generated "cancel.x" and "cancel.y" parameters. This results in KualiExceptionHandlerAction mistakenly thinking that the "submit" button was clicked when using IE (since that browser's requests do not appear to contain the non-suffixed "cancel" param, at least with IE 7).

      Modifying KualiExceptionHandlerAction to include checks for the "cancel.x" and "cancel.y" request parameters should be sufficient to fix this problem.

        Issue Links

          Activity

          Hide
          Garey Taylor added a comment -

          in KualiExceptionIncidentForm::populate i did a check for the ie. .x .y parameters and populated the "cancel" boolean.

          Show
          Garey Taylor added a comment - in KualiExceptionIncidentForm::populate i did a check for the ie. .x .y parameters and populated the "cancel" boolean.

            People

            • Assignee:
              Garey Taylor
              Reporter:
              Chad Hagstrom
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 day
                1d
                Remaining:
                Remaining Estimate - 1 day
                1d
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel