Attached test case that shows the issue.

Steps:

• Load welcomeICEfaces.jsf
• In the filter field enter a '1' and press the enter key.
• There is an ace:ajax tag set for the filter event which will show what component is active for onStart, onSuccess, and OnComplete
• The onStart shows the filter field has focus.
• Then the onSuccess and onComplete show focus set to a button outside of the table.

Note when testing with the most recent EE 3.3.0 branch, I am not able to see the onSuccess and onComplete events being fired in IE.

Cancel default action when Enter key is pressed to avoid having form submitted by ICEfaces' form capturing feature (the filtering input has its own submitting callback). Also registered the filtering callback on keydown instead of keypress to capture the Enter key in IE (keypress callback is not invoked on Enter keypress).

Tested with ICEfaces 4 trunk r44662. Focus is still moving to button.

Tested with ICEfaces EE-3.3.0_P03 tag and maintenance branch r44662.
IE 11 - Focus stays in the filter input but the onSuccess and onComplete events are not being fired. Also the focus moves back to the button when testing this same scenario with FF and Chrome.

Re-opened as per QA's noted regressions, also the onComplete and onSuccess issue needs attention.

Added modified test case file with callbacks that do not throw exceptions.

The onSuccess and onComplete callbacks will be fired since they do not trigger errors when document.activeElement is not defined in some browsers.

Tested with ICEfaces 4 trunk r44662 and modified test case.
When using Chrome and FF the focus is still being placed on the Button after entering input and pressing Enter.
Tested with ICEfaces EE-3.3.0.GA_P03 tag and maintenance branch r44666. Focus is retained within the text input.

In all cases the filter event is no longer firing in the modified test app.

Re-opened for issues reported in the comment above.

Updated attached test files. One of the callbacks was missing a parenthesis which triggered a JS error.

Ported forward the fix for ICE-10658 to trigger the events in the expected order.

Tested with ICEfaces 4 trunk r44668, ICEfaces EE-3.3.0.GA_P03 tag r44666 and modified test case.
When using FF and the testing steps as per the description
1.)Type 1 into the input and press enter, focus stays in the input. (_iceForm:testTable:colOne_filter)
2.) Press Enter or dismiss the JS prompt and focus is moved to the button. (_iceForm:testButton)
3.) Press Enter or dismiss the JS prompt and focus is moved back to the input area. (_iceForm:testTable:colOne_filter)

When using Chrome and the testing steps as per the description
1.)Type 1 into the input and press enter, focus stays in the input. (_iceForm:testTable:colOne_filter)
2.) Press Enter or dismiss the JS prompt and focus becomes undefined. (2_undefined)
3.) Press Enter or dismiss the JS prompt and focus is moved to the button. (3_undefined)

When testing with IE 11 the focus appears to start at, and end at the text input, with a dead zone in between. The js prompts are as follows: (_iceForm:testTable:colOne_filter), (2_null), (3_undefined).

I don't see FF behaving as described, the focus is kept on the input element at all times. As for Chrome, indeed the focus is set on the window once after the first pop up is closed. Once the messages are logged instead of showing them in popups then Chrome runs just fine, it keeps the focus on the input element.
In IE11 the second popup will show an undefined value because the DOM update is applied slightly different causing the input element to be out of the DOM temporarily.

I believe the test should be changed so that the alert popups are replaced with log calls to avoid their interference with focus.

.....
<ace:ajax event="filter"
          onStart="ice.log.debug(ice.log, '1_' + (document.activeElement ? document.activeElement.name : null)); return true;"
          onSuccess="ice.log.debug(ice.log, '2_' + (document.activeElement ? document.activeElement.name : null));"
          onComplete="ice.log.debug(ice.log, '3_' + (document.activeElement ? document.activeElement.name : null));"/>
.....

Verified using the suggested modification to the test application, ICEfaces EE-3.3.0.GA_p03 tag, ICEfaces 4 trunk r44693. Tomcat 7, IE 11, 10, 9, 8, 7, FF 34, Chrome 42.

Verified using the suggested modification to the test application, ICEfaces EE-3.3.0.GA_p03 Jenkins Build 07, Tomcat 7, IE 11, 10, 9, 8, 7, FF 34, Chrome 42