[
https://issues.apache.org/jira/browse/WICKET-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776124#comment-13776124
]
Martin Grigorov commented on WICKET-5366:
-----------------------------------------
In WICKET-5291 (the ticket that broke this functionality) I suggested a patch
that would fix this behavior but now I think it is not a good fix.
1) it doesn't cover the case with FilteredHeaderItem
2) what should be the behavior when a bundle contains two resource references
and these references are rendered with different filters
(FilteredHeaderItem#getFilterName()) ?
3) whatever we do in
org.apache.wicket.markup.head.ResourceAggregator#getItemToBeRendered to fix the
problem with (Priority|Filtered)HeaderItem it won't be able to support user
defined IWrappedHeaderItem implementations. I.e. if I have
MyHeaderItem(someOtherHeaderItem) then
org.apache.wicket.markup.head.ResourceAggregator#getItemToBeRendered will loose
the information about MyHeaderItem.
> ResourceAggregator looses information about priority/filtering/... when using
> a bundle
> --------------------------------------------------------------------------------------
>
> Key: WICKET-5366
> URL: https://issues.apache.org/jira/browse/WICKET-5366
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.11.0
> Reporter: Martin Grigorov
> Assignee: Emond Papegaaij
>
> If a resource reference is part of a bundle and this resource reference is
> rendered with PriorityHeaderItem then the bundle is not rendered with
> priority.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
