Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-1155

Same event ID is generated for EventListener rendered within loop

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.1.1
    • Fix Version/s: 4.1.1
    • Component/s: tapestry-core
    • Labels:
      None
    • Environment:
      Not environment related

      Description

      I have use the EventListener with the use of target while the target is rendered within a For. The script can generate multiple javascript with different clientId but the event ID are the same.

      ComponentEventConnectionWorker.getEvents function need to include the clientId during hash generation to prevent duplicated event ID for component. But I also found that this method is also called by renderBody method besides linkComponent. So I don't know whether the fix is adding a String as parameter for initial hash and pass target (renderBody) and clientId(linkComponent) to generate the initial hash value.

        Attachments

          Activity

            People

            • Assignee:
              jkuhnert Jesse Kuhnert
              Reporter:
              andyyeung Andy Yeung
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: