Tapestry
  1. Tapestry
  2. TAPESTRY-1391

@EventListener method in component doesn't rewind the containing page's client-persistent properties

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.1.1
    • Fix Version/s: 4.1.2
    • Component/s: XHR/dhtml/Ajax
    • Labels:
      None

      Description

      it appears that if a component has an event listener method which listens for events on objects within that component, but has parameters bound to values on the containing page, when that listener is invoked the component is rewound and its properties are updated – and propagated to the containing page, but that page has not been rewound at all with its own client-persistent properties. this causes all sorts of unexpected behavior where components are attached to completely random or uninitialized page objects.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            John A. Gregg
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development