Tapestry 5
  1. Tapestry 5
  2. TAP5-1046

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

    Details

    • 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:
      None

      Description

      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.

        Activity

        There are no comments yet on this issue.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development