[WICKET-1095] invisible TransparentResolver skips markup of visible children and thus resulting in an exception in Page#checkRendering (component not found in markup)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0-beta4
• Fix Version/s: 1.3.0-rc1
• Assignee: Johan Compagner
• Reporter: Gerolf Seitz
• Created: 22/Oct/07 23:34
• Updated: 01/Nov/07 09:44
• Resolved: 31/Oct/07 23:25

Description

the code involved can be found at http://papernapkin.org/pastebin/view/13287

if a transparent (= isTransparentResolver()

{return true;}

) markupContainer is set to invisible, the component's markup is skipped (markupStream.skipComponent() in Component.java line 2319).
if the parent containing the transparent markupContainer is added to the ajax request target and there is a component (in this case a button) "inside" the transparent markupcontainer's markup but is actually a child of the transparent markupcontainer's parent, the button is never actually rendered (due to skipping the markup of the transparent webmarkupcontainer) but is still visibleInHierarchy (see Page.java line 1005), because the invisible transparent markupcontainer is not a parent of the button.

the ultimate question is: what is the desired behavior for an invisible transparentResolver? render it's "children" or not?