[
https://issues.apache.org/jira/browse/TAP5-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856336#action_12856336
]
Ciaran Wood commented on TAP5-722:
----------------------------------
>From the looks of that revision diff you linked to, the offending line of code
>has gone. My patch included a selenium test to test this behaviour, maybe this
>could be added to the test suite?
> Tapestry ajax form swallows server-side errors
> ----------------------------------------------
>
> Key: TAP5-722
> URL: https://issues.apache.org/jira/browse/TAP5-722
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Ciaran Wood
> Attachments: TAP-722.patch
>
>
> I've encountered a bug in T5.1.0.5 where a form that submits via ajax (i.e.
> The form has its zone parameter set) will never notify the user if the
> server-side action fails. I've traced it down to this line in tapestry.js:
> // Set a default failure handler if none is provided.
> options.onFailure |= Tapestry.ajaxFailureHandler;
> This line is in the sendAjaxRequest function that gets added to all form
> elements via Prototype's Element.addMethods function. I used firebug to
> debug the above statement and instead of the OR assignment that it looks
> like, options.onFailure actually ends up being assigned the value '0'. I
> guess this means that its only a bitwise operation and can't be used for
> functions etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
