[
https://issues.apache.org/jira/browse/WICKET-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178353#comment-14178353
]
Andrea Del Bene commented on WICKET-5730:
-----------------------------------------
I've found this issue while I was tring to port my main app from 6.x to 7.x.
Most of the problems were related to Enclosure and Border component. To solve
the problem I've expanded markup filters HtmlHandler and
RelativePathPrefixHandler. I've also refactored a little bit the component
queuing code.
PS: I've forgotten to add a test case for the issue :).
> Dequeue auto component can't resolve components if they are nested in child
> markup
> ----------------------------------------------------------------------------------
>
> Key: WICKET-5730
> URL: https://issues.apache.org/jira/browse/WICKET-5730
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 7.0.0-M3
> Reporter: Andrea Del Bene
> Assignee: Andrea Del Bene
> Fix For: 7.0.0-M4
>
> Attachments: QueueBorder.tar.gz
>
>
> If a container has an auto component (ex: enclouse) in its markup but this
> later is nested inside a child, the autocomponent won't be resolved if child
> is a IQueueRegion. For example (taken from quickstart):
> {code}
> <span wicket:id="myBorder">
> bar
>
> <wicket:enclosure>
> <span wicket:id="c">c</span>
> </wicket:enclosure>
> </span>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
