Attached a screenshot of the Chrome console and stack when the error occurs.

Linking to the parent JIRA for MyFaces 2 compatibility.

The debugging gets pretty nasty with the functions and closures and such. The general problem is that when the <a> anchor wrapped around the image is clicked, the parent form cannot be found. This only occurs after a successful update has been applied which is why it alternating clicks succeed/fail/succeed/fail, etc.

Perhaps when the update gets applied, a listener or handler doesn't get properly re-registered.

We submitted a table updating fix to Mojarra, this may be related here as well.

Verify that this may be similar to the same table update issue we had with Mojarra. Open a JIRA an provide a patch if necessary.

The issue occurs when the element triggering the submission is captured by our form AJAX hijacking in the 'onsubmit' handler but the form is instead submitted by MyFaces JS code using form's 'submit' function. When another submit is triggered in the same form MyFaces will invoke the 'onsubmit' callback because now it's defined. The element captured in the 'onsubmit' callback during the previous submit is not attached to the document anymore, hence the failure of finding the parent form.

Fallback to using form as submitting element when the element was removed by a previous update and form.onsubmit callback is called directly (by application or third party library code).