I think this change is controversial: several people have voiced their concerns regarding this change. It is something we have been opposed to until very recently (label with <span/>). You propose to change markup that is outside Wicket's control, I think that is a slippery slope and I advise against it, hence my -0.9.
A <div /> does have a different meaning in XML versus HTML. We shouldn't just go about and muck things up. I've done some digging in firefox's bugzilla and found: - https://bugzilla.mozilla.org/show_bug.cgi?id=327637 - https://bugzilla.mozilla.org/show_bug.cgi?id=369609 - https://bugzilla.mozilla.org/show_bug.cgi?id=135425 where the first 2 are marked as dupes for the last one. After reading this and the firefox developers I think the <div /> element used in these cases is a user bug, and therefore my comparison to fixing spelling errors still holds. Does this buggy behavior still exist when you serve the page as XML? So if you go ahead make sure it works for XML, XHTML and HTML documents. Martijn -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
