[
https://issues.apache.org/jira/browse/WICKET-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-4313.
-------------------------------------
Resolution: Fixed
Fix Version/s: 6.0.0
Assignee: Martin Grigorov
> Possibility to move certain HeaderItems to the front
> ----------------------------------------------------
>
> Key: WICKET-4313
> URL: https://issues.apache.org/jira/browse/WICKET-4313
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.0.0
> Reporter: Emond Papegaaij
> Assignee: Martin Grigorov
> Fix For: 6.0.0
>
> Attachments: 0001-WICKET-4313-priority-header-item.patch
>
>
> With the patch for WICKET-4000, the order of header items has become more
> predictable, but it also has become more difficult to declare header items
> that are used by many other components. Of course, the preferred way to do
> this, would be to declare the resource as a dependency for the other
> resources, but this may prove to be difficult in some applications. The patch
> in this ticket adds support for a PriorityHeaderItem. These items are
> rendered at the top of the header in a parent-first order. This makes it
> possible to declare these resources in the page, which makes them available
> for all components.
> In addition to the PriorityHeaderItem, this patch makes it possible to move
> the page header (<head> and <wicket:head>) to the top of the header (just
> below the priority items), rather than at the bottom of the header. This is
> more like Wicket 1.5 used to render the header. By default the items are
> still rendered in a strict child-first order.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
