and experimenting, I finally
found the culprit... yep; p tags. When any of my sub-components of
mainPanel were wrapped in p tags, it caused the parent to duplicate
instead of replace. Replace the p tag with a div and everything works
fine. So obviously I have a perfectly good solution!
Does anyone
Could it be related to
http://stackoverflow.com/questions/10763780/putting-div-inside-p-is-adding-an-extra-p
?
I've seen odd behavior before when using block-level elements inside p-tags.
However, from your e-mail it's not entirely clear what your html looks
like. Subcomponents of mainpanel
be a Wicket issue per se, more of DOM or JQuery
issue, that had a weird knock-on effect on Wicket. I was wondering if Wicket
people had experience of it.
I think the upshot of this; don't use p tags for random formatting! :)
Thanks Martin and Bas - all interesting stuff - I appreciate your inputs
.
After tons of reverting on code, hacking and experimenting, I finally found the
culprit... yep; p tags. When any of my sub-components of mainPanel were
wrapped in p tags, it caused the parent to duplicate instead of replace.
Replace the p tag with a div and everything works fine. So obviously I
