The additional information was logged by QA:

(Chrome) - Browser console error upon launch of application:
Uncaught Error: jsf.ajax.request: source not set ......
request jsf.js.jsf?ln=javax.faces&v=4_0_0_140804:1
im.viewManager.showView VM799:6784
onclick showcase-mobile.jsf:25

(FF) Pressing the Enable Cloud Push button causes a navigation error in FF:
"Firefox doesn't know how to open this address, because one of the following protocols (icemobile) isn't associated with any program or is not allowed in this context."

(IE11) - Browser console error upon launch of application:
SCRIPT5022: jsf.ajax.request: source not set
File: jsf.js.jsf, Line: 1, Column: 32071.
Pressing the Enable Cloud Push button causes a navigation error

I was able to see the problem with other demo besides Cloud Push as well. According to the work done in ICE-9838, Art was also seeing a JavaScript error when he first added the Cloud Push component demo. According to his notes in that case:

"It only happens once or twice, and it doesn't seem to affect functionality. It only happens when resource coalescing is on. If you remove the very last h:outputText on the page, the error doesn't occur."

This js error is seen in all showcase-mobile demos since around the time of revision 42057. Additional issue that is occurring since that revision is the top left corner navigation is no longer rendered on the demos when viewed on a mobile device.

Modified ice.mobi.viewManager.showView function to pass in the submitting form (as the javax.faces.source parameter) when calling jsf.ajax.request function. This avoids having the warning Mojarra bridge issues.

Verified Icefaces 4 trunk r42085. Tomcat 7, all browsers. All issues resolved except for the navigation errors in FF and IE when using the Enable Cloud Push button.

Please take a look at the navigation errors noted by QA.

When Enable Cloud Push button is clicked the browser navigates to a URL that uses icemobile: protocol. This protocol is normally implemented by our ICEmobile containers (for different devices). The desktop browser does not know anything about this protocol, hence the error.

This problem should maybe solved in the demo app by hiding the button when running in a desktop browser.

The cloudPush issue has been spun off into ICE-10211.

Marking this issue Resolved.