You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2014/08/28 00:28:58 UTC
[jira] [Closed] (TAP5-2048) Ajax behavior for links/forms separate
from Zone updates
[ https://issues.apache.org/jira/browse/TAP5-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-2048.
--------------------------------------
Resolution: Invalid
> 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)