[
https://issues.apache.org/jira/browse/WICKET-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509357
]
Juergen Donnerstag commented on WICKET-695:
-------------------------------------------
update: This is an inconsistency, correct.. Invisible components are not
rendered for performance reasons. I changed the Border code on my laptop to not
render <body> components if setBorderBodyVisible(false), but I have some issues
with Page.checkRendering() now which I don't know how to solve yet. The reason
is that we resolve the <body> tag and its content without attaching a
WebMarkupContainer to it and we are not re-assigning the border child
components (insight <span wicket:id="border"> to that body container. And what
makes it even more difficuilt, components added to <wicket:border> are also
children of the same Border container. We only find out at render time who is
who.
Juergen
> Border.resolve() should not attempt to render contents if bodyVisible is false
> ------------------------------------------------------------------------------
>
> Key: WICKET-695
> URL: https://issues.apache.org/jira/browse/WICKET-695
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta1, 1.3.0-beta2, 1.3.0-beta3
> Reporter: Stefan Kanev
> Assignee: Juergen Donnerstag
> Priority: Minor
>
> Border.resolve() should not attempt to render its nested components if
> setBorderBodyVisible(false) has been called. This way the behavior would be
> similar to Component.setVisible() - when the contents are not visible, wicket
> would not raise an exception if there are no corresponding components for the
> border's markup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
