G'day! When using an eventlink like so:
<t:eventlink event="deleteComment" t:mixins="confirm" async="true" context="comment.id" class="btn btn-danger btn-xs" message="${message:confirm.delete.comment}"> ${message:delete} </t:eventlink> The browser sends two xhr requests for the deleteComment event. Removing the async and adding a zone parameter, like below, fixes this: <t:eventlink event="deleteComment" t:mixins="confirm" zone="^" context="keyword.id" class="btn btn-danger btn-xs" message="${message:confirm.delete.comment}"> ${message:delete} </t:eventlink> Likewise, if I remove the confirm mixin and leave the async="true", then it only sends one xhr event as expected (but without the confirm modal of course). Is this expected? Why is this happening? -- Casey Link Outskirts Labs { https://outskirtslabs.com } Technology for Changemakers --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org