[
https://issues.apache.org/jira/browse/TAP5-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-1046.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.2.0
> Change Tapestry client-side JavaScript to make the tapx/Confirm component
> easier to implement
> ---------------------------------------------------------------------------------------------
>
> Key: TAP5-1046
> URL: https://issues.apache.org/jira/browse/TAP5-1046
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.0
>
>
> The tapx/Confirm component needs to "hook into" links and submit components,
> in order to hook up the confirmation. As currently implemented, this
> requires
> too much internal knowledge of the tapestry.js internals.
> The approach I've been taking is to replace a simple "click" event handler
> into two parts: a "click" event handler that cancels the event and fires a
> "tapestry:action" event, and a handler for the "tapestry:action" event.
> Using this, tapx/Confirm can override the default "click" event handler, but
> get back to the original logic after confirmation by firing the
> "tapestry:action' event.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
