[jira] [Commented] (TAP5-2048) Ajax behavior for links/forms separate from Zone updates

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade commented on TAP5-2048:
--------------------------------------

I think this can be closed (see 24534b3dd0e6e492049525b2884bfd3e5fb01666, TAP5-1404).

> Ajax behavior for links/forms separate from Zone updates
> --------------------------------------------------------
>
>                 Key: TAP5-2048
>                 URL: https://issues.apache.org/jira/browse/TAP5-2048
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Howard M. Lewis Ship
>              Labels: ajax
>
> Increasingly, link a form or link to a Zone to perform an update is awkward: in some cases, the server-side behavior will limit its response to messages via AlertManager; in other cases, the update will be for multiple Zone's with well-known client ids, via the AjaxResponseRenderer service.
> It would be nice if there was a parameter or mixin that forced a Form, ActionLink, or EventLink to be an Ajax request without specifying a zone.
> Ultimately, this should be no more than a data- attribute and a document-level event handler.



--
This message was sent by Atlassian JIRA
(v6.2#6252)