well, ive given my opinion and you have given yours. in component frameworks it is very difficult to use ids because components are reused and composited, and managing all those ids by hand will be very tedious and you will still probably end up with duplicate ones in the produced html.
we do, however, support component.setmarkupid() that lets you set your own... -igor On Thu, Mar 6, 2008 at 10:03 AM, gomera <[EMAIL PROTECTED]> wrote: > > Sorry man, but your recommendation is not valid at all. An ID selector is > much more important than a class selector and it is used for different > things. > > Changing the HTML just because Wicket throws away my ids it is something > very frustrating and doing this from Java is not an option. > > My workaround: Still using 1.2.6 until it is fixed :,( > > > > igor.vaynberg wrote: > > > > my recommendation has always been to let wicket generate the ids. > > > > the css argument is invalid imho because you can just as easily use a > > class > > instead of id > > > > -- > View this message in context: > http://www.nabble.com/getMarkupId-doesn%27t-return-the-id-from-the-markup-tp11277169p15879983.html > > > Sent from the Wicket - Dev mailing list archive at Nabble.com. > >
