Tapestry 5
  1. Tapestry 5
  2. TAP5-1046

Change Tapestry client-side JavaScript to make the tapx/Confirm component easier to implement


    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.2.0
    • Component/s: tapestry-core
    • Labels:


      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.


        Howard M. Lewis Ship created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Status In Progress [ 3 ] Closed [ 6 ]
        Fix Version/s 5.2.0 [ 12314122 ]
        Resolution Fixed [ 1 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        6m 5s 1 Howard M. Lewis Ship 06/Mar/10 02:18
        In Progress In Progress Closed Closed
        1h 31m 1 Howard M. Lewis Ship 06/Mar/10 03:49


          • Assignee:
            Howard M. Lewis Ship
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: