You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2013/07/25 23:11:48 UTC
[jira] [Closed] (TAP5-1570) More javascript events for zones
[ https://issues.apache.org/jira/browse/TAP5-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1570.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.4
Assignee: Howard M. Lewis Ship
Tapestry 5.4 now defines a number of events to force a zone to update, or to be informed of its progress.
> More javascript events for zones
> --------------------------------
>
> Key: TAP5-1570
> URL: https://issues.apache.org/jira/browse/TAP5-1570
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.1.0.0, 5.1, 5.0.16
> Reporter: Joe Klecko
> Assignee: Howard M. Lewis Ship
> Fix For: 5.4
>
>
> It seems that time and time again for each T5 project (6 out of 7 so far) I find I need to override tapesty.js methods to add additional support for zones. Currently there is only 1 event fired from a zone (Tapestry.ZONE_UPDATED_EVENT), I'd like to suggest/request there be at least 4 events total (3 new ones):
> 1) ZONE_BEFORE_AJAX_REQUEST_EVENT: This would be fired before the ajax request is sent to the server. Listeners should be able to cancel the ajax request (similiar to the way tapestry allows a form submission to be canceled)
> 2) ZONE_BEFORE_UPDATE_EVENT: This would be fired after the ajax request returns and just before the zone is updated via the processReply() method. Again, listeners should be able to cancel the update.
> 3) ZONE_UPDATED_EVENT: already and is listed here for completeness.
> 4) ZONE_AJAX_REQUEST_ERROR_EVENT: This would be fired if the ajax request errored out for the zone. (includes error data)
> references to mailing list: http://tapestry.1045711.n5.nabble.com/More-javscript-zone-events-please-td4401005.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira