[WICKET-5479] Header rendering of components inside of InlineEnclosure

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.13.0
• Fix Version/s: 7.0.0-M1
• Labels: enclosure
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Fridolin Jackstadt
• Created: 21/Jan/14 17:48
• Updated: 05/Mar/14 10:02
• Resolved: 05/Mar/14 10:02

Description

AjaxLink inside of an InlineEnclosure doesnt work, if container is made visible via ajax.
It is possible to use a WebMarkupContainer instead as workaround.

The Question is: should the InlineEnclosure work, which looks straight forward to me, or is this problem hard to fix and I should keep using the workaround?

Issue Links

• is related to: WICKET-4874 "Cannot find element with id" error seen in Ajax Debug for child of wicket:enclosure
• is related to: WICKET-3335 Component Queueing (extract hierarchy information from markup)