You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Meier (Jira)" <ji...@apache.org> on 2019/09/11 17:29:00 UTC
[jira] [Resolved] (WICKET-6673) PriorityHeaderItem ordering is
wrong for siblings
[ https://issues.apache.org/jira/browse/WICKET-6673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sven Meier resolved WICKET-6673.
--------------------------------
Resolution: Fixed
Thanks to Sebastien for spotting a problem with the new implemtation. This is fixed now.
> PriorityHeaderItem ordering is wrong for siblings
> -------------------------------------------------
>
> Key: WICKET-6673
> URL: https://issues.apache.org/jira/browse/WICKET-6673
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 9
> Reporter: Sven Meier
> Assignee: Sven Meier
> Priority: Minor
> Fix For: 9.0.0-M3
>
>
> PriorityHeaderItems allows parents to move their header items infront of those of their children (_parent-first_ instead of _child-first_).
> But the current implemention sorts PriorityHeaderItems of siblings in reverse order, e.g. having a component hierarchy as follows:
> {code:java}
> Component A
> +- Component AA
> +- Component AB
> {code}
> ... the PriorityHeaderItems of all these components are sorted as:
> {code:java}
> - PriorityHeaderItem of A
> - PriorityHeaderItem of AB
> - PriorityHeaderItem of AA
> {code}
> Why should the PriorityHeaderItem of component AB be before that of AA? This isn't _parent-first_, it is _reverse-order_.
> IMHO a more suitable ordering would be "_parent-first-preserving-siblings"_:
> {code:java}
> - PriorityHeaderItem of A
> - PriorityHeaderItem of AA
> - PriorityHeaderItem of AB
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)