That's precisely why that method/functionality exists. If you have a
component which is not visible on the first render, how can wicket
"replace" it on subsequent ajax renders?
When you call setOutputMarkupPlaceholderTag(true), wicket will render a
tag with style="display:none" which provides wicket's ajax library with
a hook in the dom.
Suppose you don't call that method, there will be no element in the dom
which can be replaced.
Met vriendelijke groet,
Kind regards,
Bas Gooren
schreef Jared Sol op 25-10-2013 23:03:
No problem. I'm not exactly sure. I just know when hiding an element and then
unhiding it you have to tell the component to keep a placeholder so it doesn't
lose access to the component when you hide it. Might have something to do with
keeping it around in the dom and using display=none. I haven't looked into the
details.
Sent from my iPhone
On Oct 25, 2013, at 11:45 AM, dhongyt <[email protected]> wrote:
Thanks you! That worked for me. What is the reason for this? Is this so that
it would it would hold the placeholder with in wmc?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Displaying-ListView-After-Being-Hidden-tp4661963p4661972.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
