The fixes for ICE-10176 and the modification made to the demo page to have ace:selectMenu submit the focused component selection on value change should have fixed the icecore:focusManager demo.

Here are the steps to test Forward button:

• Select icecore:navigationNotifier demo page.
• Click on 'Navigate to the other page' link.
• Click the 'link' link (on the second row of text).
• Click the browser's 'Back' button.
• Click the browser's 'Forward' button.
• Check if navigation was detected.

ICEfaces4 trunk rev. 42310:
1) A server warning is seen when accessing the showcase/showcase-core.jsf page:
WARNING: JSF1063: WARNING! Setting non-serializable attribute value into HttpSession (key: coreMenu, value class: org.icefaces.samples.showcase.view.navigation.CoreMenu).

2) icecore:jsEventListener fails to capture the "keypress" event in IE10/11 and Chrome36; not an issue in FF31.

3) icecore:navigationNotifier
In IE10 JS errors occur when loading this component from drop-down on /showcase-core.jsf page; this demo fails to render in IE10.

Message: Access is denied.
Line: 1909
Char: 13
Code: 0
URI: http://10.18.39.149:8080/showcase/javax.faces.resource/jsf.js.jsf?ln=javax.faces&stage=Development&v=4_0_0_140826

Message: Unable to get property 'iframeLoaded' of undefined or null reference
Line: 43
Char: 13
Code: 0
URI: http://10.18.39.149:8080/showcase/javax.faces.resource/navigation-notifier/blank.html.jsf?

1) Made CoreMenu bean serializable to alleviate JSF warnings.

2) Some keypress events are captured by the browser itself when running in IE or Chrome. This is a known limitation, keydown should be used instead to capture any key type event.

3) Modified rsh.js to create iframe element needed by IE to use DOM API instead of writing markup into the parsed document. This element creation method does not trigger "Access denied" errors in IE10.