You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Claudia Hirt (JIRA)" <ji...@apache.org> on 2017/05/25 19:34:04 UTC
[jira] [Created] (WICKET-6377) Autolinking breaks hierarchy for
nested elements
Claudia Hirt created WICKET-6377:
------------------------------------
Summary: 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: 8.0.0-M6, 7.6.0
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)