[
https://issues.apache.org/jira/browse/WICKET-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025340#comment-16025340
]
ASF subversion and git services commented on WICKET-6377:
---------------------------------------------------------
Commit 86b3abad1fa2813c80c0c3fa73c4248cc4033301 in wicket's branch
refs/heads/master from [~bitstorm]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=86b3aba ]
WICKET-6377 Autolinking breaks hierarchy for nested elements
> Autolinking breaks hierarchy for nested elements
> ------------------------------------------------
>
> Key: WICKET-6377
> URL: https://issues.apache.org/jira/browse/WICKET-6377
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 7.6.0, 8.0.0-M6
> Reporter: Claudia Hirt
>
> The problem appears with the following HTML-code:
> {code:xml}
> <a href="#top">
> <span wicket:id="top"></span>
> </a>
> {code}
> with autolinking set to true like this:
> getMarkupSettings().setAutomaticLinking(true)
> This leads to the following exception:
> org.apache.wicket.markup.MarkupException: Unable to find component with id
> 'top' in [WebMarkupContainer [Component id = _autolink_-335431082]] Expected:
> '_autolink_-335431082:top'.
> This happens since the the fix of WICKET-6289. The bugfix in this issue was
> to create a WebMarkupContainer as default autocomponent. It was and
> ExternalLink before, which didn't cause any trouble in this case.
> But is it really correct that AutoLinkResolver even tries to replace an
> anchor link?
> I also created a quickstart project to reproduce the problem:
> https://github.com/sunshineKE/test.autolinking
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
