You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2016/10/25 07:16:59 UTC

[jira] [Resolved] (WICKET-6259) Does not effect "x-ua-compatible" of the meta element

     [ https://issues.apache.org/jira/browse/WICKET-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-6259.
-------------------------------------
    Resolution: Not A Problem

Please use the mailing lists (http://wicket.apache.org/help/email.html#user) for questions!
Thank you!

> Does not effect "x-ua-compatible" of the meta element
> -----------------------------------------------------
>
>                 Key: WICKET-6259
>                 URL: https://issues.apache.org/jira/browse/WICKET-6259
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.19.0, 7.5.0
>            Reporter: Tomonori Matsuda
>
> I useWicket6
> Does not effect "x-ua-compatible" of the meta element
> The head element of the HTTP response body generated by Wicket, sometimes elements are arranged in the following order.
> 0. head element
> 1. ref to .js file of the script "jquery"
> 2. Contents that has been described in AbstractPage.html(title, etc.)
> To AbstractPage.html, described the "x-ua-compatible", we expect that the document mode of Internet Explorer (IE) is controlled.
> Prior to the reading of "x-ua-compatible", when the reading of external resources occurs, the document mode of IE at the time has been determined, 
> "x-ua-compatible" is control of does not become effective.
> Even latest Wikcet7, as long as they see a sample page, it becomes similar described order.
> http://examples7x.wicket.apache.org/index.html
> In the application you are creating in Wicket4,
> 2. And 1. the order of the inverse, "x-ua-compatible" You have been working normally.
> .js the description read of external resources, such as, Is there a way to change after the "title" element?
> Or hope the software modifications as to the standard of such behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)