On Fri, Mar 7, 2008 at 3:27 AM, juan.pablo.coen.mitrani <[EMAIL PROTECTED]> wrote: > igor.vaynberg wrote: > > > > wicket does not take ownership of id attributes by default, you have > > to explicitly call setoutputmarkupid(true) on the component. > > > > [...] > > > > > not true, see above. and i am not aware of any change in > > policy...wicket still doesnt touch anything by default > > > > In fact, in Wicket 1.3.1 some components, like Form and Button, call > setOutputMarkupId(true) in their constructors (so it is not easily > overridable for all instances) and this was not like that in the previous > version that I was using (1.2.6).
well, 1.2.6 doesnt support nested forms, doesnt support setting the default submit button for the form, doesnt support submitlink, etc. you see where im heading with this? these changes dont just happen because we feel like it. that said, we are looking at a way to reduce this at least for the Button/SubmitLink.... -igor > > ----- > Juan Pablo Coen Mitrani > -- > View this message in context: > http://www.nabble.com/getMarkupId-doesn%27t-return-the-id-from-the-markup-tp11277169p15891162.html > > > Sent from the Wicket - Dev mailing list archive at Nabble.com. > >
