You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/01/19 14:59:34 UTC

[jira] [Commented] (TAP5-1592) Refactor AjaxFormLoop, RemoveRowLink and AddRowLink to make mixin useful for these components

    [ https://issues.apache.org/jira/browse/TAP5-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282520#comment-14282520 ] 

Jochen Kemnade commented on TAP5-1592:
--------------------------------------

The way the AjaxFormLoop and related components are rendered will change substantially in Tapestry 5.4. The configuration is done via data-attributes instead of parameters to the initializer function. I guess this issue will become irrelevant after 5.4 is released.

> Refactor AjaxFormLoop, RemoveRowLink and AddRowLink to make mixin useful for these components
> ---------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1592
>                 URL: https://issues.apache.org/jira/browse/TAP5-1592
>             Project: Tapestry 5
>          Issue Type: Sub-task
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Markus Jung
>            Priority: Trivial
>              Labels: javascript, patch
>         Attachments: ajaxFormLoopProtection.diff
>
>
> The AjaxFormLoop component stores the links in the intitializer call map. In order to modify them in a mixin in the afterRender phase, a public getter for the JavaScriptSupport interface and the JavaScriptSupportImpl class is required.
> I need this feature for the cross-site request forgery protection, where I use a mixin to add a token to the rendered event links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)