Tapestry
  1. Tapestry
  2. TAPESTRY-2121

EventListener does not bind to @Select using targets parameter.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.1.5
    • Fix Version/s: 4.1.5
    • Component/s: None
    • Labels:
      None

      Description

      Setting the "targets" parameter of EventListener to a Select component's ID will not wire up any JavaScript. Using the same ID with the "elements" parameter will bind, but it will not submit the form, so it's not quite the same thing.

        Activity

        Hide
        Kevin Menard added a comment -

        The issue seems to be in the target detection logic.

        Manually binding the component to the event works just fine. For this, I copied the generated JavaScript for some other component and modified as appropriate.

        Show
        Kevin Menard added a comment - The issue seems to be in the target detection logic. Manually binding the component to the event works just fine. For this, I copied the generated JavaScript for some other component and modified as appropriate.
        Hide
        Jesse Kuhnert added a comment -

        Added call to super.cleanupAfterRender() in Select component method implementation so that the critical renderworker code is able to run.

        Show
        Jesse Kuhnert added a comment - Added call to super.cleanupAfterRender() in Select component method implementation so that the critical renderworker code is able to run.

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            Kevin Menard
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development