Reports that this might be related to JSF 2.0.2 vs. 2.0.1. Affecting IE6 also. Ted to investigate.

Confirmed clocks are not ticking in auction in IE6. Bid buttons do not generally work.

I removed icepush.jar from auction, and it works in IE6.

Tried both JSF 2.0.2 and 2.0.1 with no difference in behavior.

Suspect JavaScript interaction or connection starvation in IE.

This appears to be an icepush bug rather than a JSF 2.0 bug.

Mircea says clearing browser cookies prior to running resolves this issue.

Still failing on IE browsers:

Clocks tick for me on Firefox (perhaps this is what was
fixed by clearing the cookies).

However, with IE 6, I have verified that the notifications
are being received and retrieveUpdate() is being called
in the browser, but an exception is being thrown in this
method:

"failed to pick updates[object error]"

(Looks like the exception doesn't have a proper toString()).

Ted.

[ Permlink | Edit | Delete | « Hide ]
Ted Goddard added a comment - 14/Jan/10 04:26 PM
Using e.name and e.message, the exception appears to be:

updateException Invalid argument

So perhaps we are passing something strange to jsf.ajax.request.

Looks like that since JSF 2.0.2 when jsf.ajax.request is invoked the ID of the source element will be saved then looked up again to provide it as event parameter to the registered event listeners. If the element has no ID the call to document.getElementById function will throw an 'Invalid argument' error in IE and return null in the other browsers.

Provide fake ID to the temporary form to avoid triggering exception in IE.