You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/04/05 22:36:27 UTC

[jira] Closed: (TAP5-1096) If a Zone's id parameter is bound, then the clientId property should return that value, even before the Zone renders

     [ https://issues.apache.org/jira/browse/TAP5-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1096.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.2.0

> If a Zone's id parameter is bound, then the clientId property should return that value, even before the Zone renders
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1096
>                 URL: https://issues.apache.org/jira/browse/TAP5-1096
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.2.0
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.