I've since had a similar requirement and i found comparing
event.origionalTarget
to
event.currentTarget
solves the problem.
On 15/03/2012 8:29 AM, Paul Stanton wrote:
like i said, this could be a bug. why not log it in jira and see what
the big heads think?
On 15/03/2012 1:44 AM, nquirynen wrote:
Found a solution for my problem (not sure if it's a good solution,
but it
works):
In the update event of the parent zone (zone1 in my example) I added
an if
statement to know if it's not just an inner zone that's getting updated:
$('#zone1').bind(Tapestry.ZONE_UPDATED_EVENT, function(event) {
if(event.target['id'] == 'zone1) {
// do stuff only when zone 1 is getting updated
}
});
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Zone-update-triggers-update-on-parent-Zone-tp5541247p5564976.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
