Let's add instructions for the new dependency to the wiki page for the ace:navigationNotifier on the dependency and where to find instructions on how to solve.

Added instructions in the Wiki, see http://wiki.icesoft.com/display/IFEE2/EE4+-+WebSphere+Application+Server+8#EE4-WebSphereApplicationServer8-standaloneconfiguringtheicefacesapplication .

Tested with ICEfaces EE-4.2.0.GA build 2 on WAS 9. The application could not be launched when the beans.xml file was added to the WEB-INF directory of the showcase app. Could this be because the namespaces used in the beans.xml file are not compatible with ICEfaces 4? The "http://java.sun.com/xml/ns/javaee" namespaces are used in ICEfaces EE 3.x applications. In the ICEfaces 4 test apps the "http://xmlns.jcp.org/jsf/....." namespaces are used.

I don't think the namespace is the problem.
I could deploy and run sucesfully the showcase app on Websphere 9.0.0.2 when I built the app using the web-profile target or servlet-profile target with Myfaces. The Enterprise Applications > showcase_war > JSP and JSF options scrren actually states that only Myfaces is supported with version 9.*:

The JSF implementation is a server-wide configuration setting for Version 8.0 and later nodes. If you have multiple applications that require different JSF implementations, you must separate the applications into different application servers or clusters. For Version 7.0 nodes, the JSF implementation is an application configuration setting. For Version 9.0 and later nodes, the Sun Reference 1.2 JSF implementation is not supported. Version 9.0 and later nodes use the MyFaces JSF implementation, even if SunRI is selected in a mixed-cell environment. For more configuration information, read about JavaServer Faces in the product documentation.

Okay, I will note this requirement in the release notes.

Tested with ICEfaces EE-4.2.0.GA Build 3, WAS 9.0.0.2 on amazon AWS using showcase app.
When showcase is built with web-profile and adding the beans.xml file into the WEB-INF directory I was able to launch the showcase app and test the navigation issue. The '2017 text ' issue is resolved however the 'Navigation detected' message is not always rendered the 2nd or 3rd time using the browser forward and back buttons in Chrome 59 and IE 11. Not an issue with Firefox.

I can not launch the showcase app with this myfaces config:
showcase built with myfaces libs
beans.xml added to web-inf directory of showcase.war
jsf and jsp options set to default or myfaces 2.2
class loader set to 'Classes loaded with local class loader first (parent last)

Server error seen
[7/26/17 17:13:12:517 UTC] 00000077 CompositionUn E WSVR0194E: Composition unit WebSphere:cuname=showcase_war in BLA WebSphere:blaname=showcase_war failed to start.
[7/26/17 17:13:12:517 UTC] 00000077 MBeanHelper E Could not invoke an operation on object: WebSphere:name=ApplicationManager,process=ICEsoft_Stand-Alone_Server,platform=proxy,node=ICEsoft_Stand-Alone_Node,version=9.0.0.0,type=ApplicationManager,mbeanIdentifier=ApplicationManager,cell=ip-10-10-0-112Node01Cell,spec=1.0 because of an mbean exception: com.ibm.ws.exception.RuntimeError: java.lang.RuntimeException: com.ibm.ws.cdi.CDIRuntimeException: com.ibm.ws.cdi.CDIDeploymentRuntimeException: java.lang.RuntimeException: Service class org.apache.myfaces.cdi.view.ViewScopeContextExtension didn't implement the required interface

Seems like it isn't finding the built-in MyFaces libs but another set in the error above. To clarify, you are not deploying the myfaces jars yourself, right?

Since WAS 9 includes a suitably new Myfaces JSF version, we only need to support web-profile deployments with the built-in JSF libs on this server.

So that configuration is working, though only on Firefox.

The remaining work to be done here is to get the other browsers functioning as expected as well.

I tested sucessfully the component with the following browsers: IE10, IE11, Chrome and Firefox. Indeed the version of Safari I have (10.1.1) seems not to work.