[
https://issues.apache.org/jira/browse/WICKET-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483267
]
Igor Vaynberg commented on WICKET-365:
--------------------------------------
why is the patch setting the flag to default and then turning it off?
@@ -530,7 +534,7 @@
/** Component flags. See FLAG_* for possible non-exclusive flag values.
*/
private int flags = FLAG_VISIBLE | FLAG_ESCAPE_MODEL_STRINGS |
FLAG_VERSIONED | FLAG_ENABLED
- | FLAG_IS_RENDER_ALLOWED;
+ | FLAG_IS_RENDER_ALLOWED | FLAG_PLACEHOLDER;
/** Component id. */
private String id;
@@ -567,6 +571,8 @@
{
setId(id);
getApplication().notifyComponentInstantiationListeners(this);
+ //Default behavior : do not render placeholder
+ setFlag(FLAG_PLACEHOLDER, false);
}
> Go from setVisible(false) to setVisible(true) on a component in ajax does not
> work
> ----------------------------------------------------------------------------------
>
> Key: WICKET-365
> URL: https://issues.apache.org/jira/browse/WICKET-365
> Project: Wicket
> Issue Type: Bug
> Reporter: Vincent Demay
> Assigned To: Igor Vaynberg
> Fix For: 1.3, 2.0
>
> Attachments: component-real.txt, Component.java.365.patch.txt,
> Component.patch.txt, Component.patch.txt
>
>
> Because no tag is generated by RenderComponent when a component is not
> visible. The attach patch simply generates a <span
> id="ComponentMarkupId"></span> when component is not visible and
> OuputMarkupId true. So we can now use ajax on setVisible(false component)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
