[
https://issues.apache.org/jira/browse/WICKET-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emond Papegaaij closed WICKET-4235.
-----------------------------------
Resolution: Cannot Reproduce
Fix Version/s: 6.0.0
I tested against the latest Wicket 6.0 and it works as expected. With the
default strategy, I first get the message from the panel and then from the page
(child first). With
-DWicket_HeaderRenderStrategy=org.apache.wicket.markup.renderStrategy.ParentFirstHeaderRenderStrategy
I get the message from the page first, followed by the message from the panel
(parent first).
Be advised though that the rendering strategy is not the preferred way to put
certain header items in front. Wicket 6.0 now has a PriorityHeaderItem, which
gets rendered parent-first.
> Parent / Child HeaderRenderStrategy does not work with <wicket:head> tag
> ------------------------------------------------------------------------
>
> Key: WICKET-4235
> URL: https://issues.apache.org/jira/browse/WICKET-4235
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5.3
> Environment: Windows 7, JDK 1.6.x
> Reporter: TH Lim
> Assignee: Emond Papegaaij
> Priority: Minor
> Fix For: 6.0.0
>
> Attachments: wicket-header-bug.zip
>
>
> I was using <wicket:head> to render the child component (Wicket Panel) CSS /
> JS 1st then followed by the parent. It didn't work. It always renders the
> parent (Wicket WebPage) JS 1st. I used
> -DWicket_HeaderRenderStrategy=org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy
> or ParentFirstHeaderRenderStrategy and it rendered the same HTML output.
--
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
