This doesn't really lead anywhere. I haven't heard a single argument against replacing <div/> with <div></div> except people being anxious of wicket touching the markup.
But you should realize that without this, you can't even put <div/> inside markup because it breaks the DOM in firefox. So what's the point? I really don't think that "I don't want wicket to touch my markup" is a valid point. All Wicket does it touching the markup. So why this particular case is wrong when it doesn't break anything (I know about - If i'm wrong on this please anyone correct me), but, rather than that it fixes real problems? -Matej On 11/2/07, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > A Html error finder (IMarkupFilter) already exists but is disabled by > default. We could extend it or create a new one. Actually anybody can > create it and provide it to us. > > Juergen >
