You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2017/05/03 20:48:04 UTC
[jira] [Resolved] (WICKET-6339) Wrong implementation of
MarkupFragment.iterator()
[ https://issues.apache.org/jira/browse/WICKET-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-6339.
-------------------------------------
Resolution: Fixed
Fix Version/s: 8.0.0-M6
7.7.0
Fixing the iterator doesn't break any Wicket tests!
My apps also work fine, but we don't do anything fancy with MarkupFragments ourselves.
> Wrong implementation of MarkupFragment.iterator()
> -------------------------------------------------
>
> Key: WICKET-6339
> URL: https://issues.apache.org/jira/browse/WICKET-6339
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.2.0
> Reporter: Sven Ackermann
> Assignee: Martin Grigorov
> Fix For: 7.7.0, 8.0.0-M6
>
>
> The method returns {{getRootMarkup().iterator(startIndex, size)}}, but this only works when {{getRootMarkup() == getParentMarkup()}} or all intermediate {{MarkupFragment}}s start at index 0.
> The {{startIndex}} of all intermediate {{MarkupFragment}}s must be added, otherwise the iterator starts at a wrong index.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)