[
https://issues.apache.org/jira/browse/WICKET-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488619#comment-13488619
]
Martin Grigorov commented on WICKET-4846:
-----------------------------------------
Wicket doesn't care what is rendered first in the head.
If you need your HTML element at the top you could use PriorityHeaderItem
and/or custom IResourceSettings#setHeaderItemComparator(Comparator).
See http://wicketinaction.com/2012/07/wicket-6-resource-management
I think this ticket should be closed as "No Problem".
> meta viewport tag should be placed first in head
> ------------------------------------------------
>
> Key: WICKET-4846
> URL: https://issues.apache.org/jira/browse/WICKET-4846
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.0.0, 6.1.0, 6.1.1, 6.2.0
> Reporter: Johannes Odland
> Priority: Minor
>
> As the sequence of header contributions changed with wicket 6.0 viewport tags
> from the page are now placed after css and javascript contributed from
> subpages and components.
> The meta viewport tag must be placed before any css is loaded for media
> queries to work properly.
> Perhaps meta-tags should be placed first in head?
--
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
