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.