On Fri, Mar 7, 2008 at 3:46 AM, JP Saraceno <[EMAIL PROTECTED]> wrote: > > 100% agree. But you still should come with a solution that covers that > without touching the IDs of the components on the page that clearly won't > run into that issue.
we are all ears...we have thought about this long and hard, but maybe we are too close and missed something. ideas and patches are always welcome. -igor > > Actually, that was in fact what Wicket did until the fix for > http://issues.apache.org/jira/browse/WICKET-694 and until Form, Button and > other classes started to have setOutputMarkupId(true) in their constructors. > > > > > igor.vaynberg wrote: > > > > i do understand that. however, html ids were created using thinking > > that the entire html document is generated by a monolithic generator. > > when you use a component oriented framework as a generator for html > > something that is unique across the entire document becomes difficult > > because each component works in isolation - that is where the power of > > these component oriented frameworks comes from. > > > > -- > View this message in context: > http://www.nabble.com/getMarkupId-doesn%27t-return-the-id-from-the-markup-tp11277169p15891177.html > > > Sent from the Wicket - Dev mailing list archive at Nabble.com. > >
