You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Christophe Cordenier (JIRA)" <ji...@apache.org> on 2010/08/01 12:58:16 UTC

[jira] Assigned: (TAP5-722) Tapestry ajax form swallows server-side errors

     [ https://issues.apache.org/jira/browse/TAP5-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christophe Cordenier reassigned TAP5-722:
-----------------------------------------

    Assignee: Christophe Cordenier

> 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
>            Assignee: Christophe Cordenier
>         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.
-
You can reply to this email to add a comment to the issue online.