Verified ICEfaces EE-3.3.0.GA_P03 tag, EE-3.3.0 maintenance branch, ICEfaces 4 trunk r44630. Tomcat 7, IE 11, FF 34, Chrome 42.

Keep track of previously focus components only if they are not focused as a result of invalidity.

Test application /ICE-10601.jsf was added to:
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/focusManager

Attached modified focus-manager demo with added ace:ajax calls.

Re-opened.

My own testing using a modified IF 4 showcase demo page (attached), which adds ace:ajax tags to each of the ace:textEntry inputs, shows a scenario where the focus is being incorrectly set.

To reproduce:

1. Run the demo
2. Set the selectMenu to set focus on entry "B" (focus is set on B correctly)
3. Tab through the entry fields, see the required error correctly appear after tabbing our of entry "D" and "E"
4. If you then enter valid data into "E", and then "D", the focus will often incorrectly be set back to "B" once all fields are valid again, instead of to the next entry in the tab-order. I was using shift-tab to go backwards in the tab-order so when focus should have gone to "C", it was going to "B" instead.

Modified component to apply focus only when the chosen component is different from last focus application to avoid interfering with submits triggered during the 'blur' events. Without this provision the focus will be put back right away as described in issue ICE-9639.