On Tue, Jun 3, 2008 at 9:19 AM, jd17 <[EMAIL PROTECTED]> wrote: > > The first and most important one is the fact that per default Wicket now > makes css ids unique, which isn't even mentioned in the migration guide (Can > you please add it?). I make heavy use of css in my application and it was > really a nuisance to have to set setOutputMarkupId(false) for a lot of > controls (at least I use markup inheritance a lot, so this wasn't much of an > issue for the WebPage subclasses). I understand that the ids must be unique > and that things crash in case one makes use of nested components. But in my > whole application I do not yet make use of such nesting (of course, coming > from 1.2.6...). So I would find it much more natural if the default would be > setOutputMarkupId(false) instead of the other way around.
Take Igor's word for it, the default /is/ false! :-) There's got to be something else involved if you're seeing them being generated... /Gwyn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
