there are plenty of threads about this on the list if you are interested. the gist of the thing is that wicket changes id so that it can guarantee their uniquness since components are self contained and isolated. there are a two basic ways to deal with this: call setmarkupid(string) for components you want to control the id for, or get the id with getmarkupid() and pass that to js code.
-igor On Sat, Mar 22, 2008 at 5:13 PM, Zach Cox <[EMAIL PROTECTED]> wrote: > I've been running our app in development mode for quite a while now > and noticed that Wicket likes to append digits to the end of id > attributes specified in the html templates. I just switched to > deployment mode and now Wicket is completely changing the id > attributes. I'm using Prototype to do some JavaScript stuff, and > while I could work around this id-changing in development mode, my > entire app is broken in deployment mode. > > Is there any way to tell Wicket to use the development mode > id-changing behavior in deployment mode? Better yet, is there a way > to tell Wicket to leave the id attributes specified in html templates > alone altogether? > > Thanks, > Zach > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
