You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/06/05 20:34:21 UTC
[jira] [Commented] (TAP5-2124) events.zone.refresh must be
triggered directly on zone element, can fail otherwise
[ https://issues.apache.org/jira/browse/TAP5-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676205#comment-13676205 ]
Hudson commented on TAP5-2124:
------------------------------
Integrated in tapestry-trunk-freestyle #1079 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/1079/])
TAP5-2124: Support triggering zone update/refresh via nested element (Revision 52fcb51f170fff5c2144a4dab7bcd3b9aad44af3)
Result = FAILURE
hlship :
Files :
* tapestry-core/src/main/coffeescript/org/apache/tapestry5/t5-core-dom-prototype.coffee
* tapestry-core/src/main/coffeescript/META-INF/modules/t5/core/events.coffee
* tapestry-core/src/main/coffeescript/org/apache/tapestry5/t5-core-dom-jquery.coffee
* tapestry-core/src/main/coffeescript/META-INF/modules/t5/core/zone.coffee
> events.zone.refresh must be triggered directly on zone element, can fail otherwise
> ----------------------------------------------------------------------------------
>
> Key: TAP5-2124
> URL: https://issues.apache.org/jira/browse/TAP5-2124
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Howard M. Lewis Ship
> Labels: javascript, zone
>
> Triggering the events.zone.refresh or events.zone.update events on an element nested within a Zone's element will fail; the document-level event handlers expect this to be the ElementWrapper for the zone element, but is instead the ElementWrapper for the triggering element.
> Currently, it is necessary for triggers to select up the tree to find the Zone's element; this should be incorporated into the document event handlers instead.
--
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