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.