You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2008/02/13 04:52:08 UTC

[jira] Updated: (WICKET-1341) Make markup id available at any point in component's lifecycle rather than only during and after first render

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

Igor Vaynberg updated WICKET-1341:
----------------------------------

    Summary: Make markup id available at any point in component's lifecycle rather than only during and after first render  (was: Improve markup id generation so it is available at component creation time instead of render time)

> Make markup id available at any point in component's lifecycle rather than only during and after first render
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-1341
>                 URL: https://issues.apache.org/jira/browse/WICKET-1341
>             Project: Wicket
>          Issue Type: Improvement
>    Affects Versions: 1.3.1
>            Reporter: Igor Vaynberg
>            Assignee: Igor Vaynberg
>             Fix For: 1.3.2
>
>
> currently component.getmarkupid() depends on page which causes users to have to call it only during render (when the hierarchy is complete and  the page is available to all components). this causes a lot of inconvenience, it would be a big improvement if getmarkupid() could generate a unique id at any point in page's/component's lifecycle.

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