hmm, makes sense - there is no global way to get rid of these empty div's ? (putting a .setRenderBodyOnly(true) to every seems quite a pain)
> -----Ursprüngliche Nachricht----- > Von: Martijn Dashorst [mailto:[EMAIL PROTECTED] > Gesendet: Sonntag, 27. Mai 2007 22:13 > An: [email protected] > Betreff: Re: wicket 1.3.0 snapshot / wicket tags in div > > Intention. Read the javadocs. > > What you are proposing is changing the meaning of the > document without any idea: what would happen if: > <h1 wicket:id="foo">[foo]</h1> > > is used? Would setStripWicketTags remove the <h1> too? > > Component#setRenderBodyOnly(boolean) is what you are looking for. > > Martijn > > On 5/27/07, Korbinian Bachl <[EMAIL PROTECTED]> wrote: > > Hi, > > > > i've come across a behaviour, that IMHO is wrong: > > > > when i have a wicket label e.g: > > > > HTML: > > > > <div wicket:id="foo"> bla bla </div> > > > > adn use it as new Label("foo", "bar") in dev, he puts out: > > > > result: <div wicket:id="foo">bar</div> > > > > wich is right; however if i do: > > getMarkupSettings().setStripWicketTags(true); > > > > in the init he puts out: > > > > result: <div>bar</div> > > > > which is blowing up HTML-output for nothing - IMHO if the tags are > > empty after the wicket:id has been stripped they should be > removed completely. > > > > Is this behavoir intention or a bug? > > > > > > > > > -- > Join the wicket community at irc.freenode.net: ##wicket > Wicket 1.2.6 contains a very important fix. Download Wicket now! > http://wicketframework.org >
