Tapestry 5
  1. Tapestry 5
  2. TAP5-1096

If a Zone's id parameter is bound, then the clientId property should return that value, even before the Zone renders

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.2.0
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      Ah, leaky abstractions. My client has a component that takes a Zone as a parameter. The component renders a Form, then the Zone, and wires the Form to update the Zone (via the Form's zone parameter). Problem is, the Zone's clientId is null when the Form is rendered, so the client-side JS to wire the Form to the Zone doesn't occur.

        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