tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Harner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1366) Tapestry must honor the position of added tags in the <head> relative to the <meta> tags, for IE compatibility
Date Thu, 18 Aug 2011 18:24:28 GMT

    [ https://issues.apache.org/jira/browse/TAP5-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087172#comment-13087172
] 

Bob Harner commented on TAP5-1366:
----------------------------------

Although this issue is now fixed for Tapestry 5.3, Tapestry 5.2 users still need a solution
for the IE Compatibility Mode issue. I just wanted to add that I have found success with the
simple code described by Wulf Wechsung at http://tapestry.1045711.n5.nabble.com/t5-adding-http-header-td3369097.html
-- it works perfectly for setting the IE Compatibility Mode header.

> Tapestry must honor the position of added tags in the <head> relative to the <meta>
tags, for IE compatibility
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1366
>                 URL: https://issues.apache.org/jira/browse/TAP5-1366
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.2
>            Reporter: Ville Virtanen
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.3
>
>
> This problem was discussed with Thiago on mailing list, reference to it:
> http://tapestry.1045711.n5.nabble.com/X-UA-Compatible-amp-IE-9-td4406801.html
> In short, the following was agreed on:
> "Wouldn't Tapestry reordering <head> elements come in the <title>, <meta>,
  
> everything else order be sufficient?"
> Old description:
> As Microsoft documentation states (http://msdn.microsoft.com/en-us/library/cc817574.aspx)
the META tags that direct IE8 must be positioned as follows: "The X-UA-compatible header is
not case sensitive; however, it must appear in the Web page's header (the HEAD section) before
all other elements, except for the TITLE element and other META elements.".
> The most flexible solution would be to honor the order of META and other tags that author
has put directly to the template: the place for T5 tags could be indicated with special tag:
> For an example 
> <html>
>   <head>
>      <title>My Web Page</title>
>       <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
>       <t:headcontent />
>       <link href="dirlang.html" rel="next"/>
>   </head>
>   .
>   .
> If author decides to omit the t:headcontent tag then T5 would not attach any meta or
link tags.
> Other solution as Howard indicated in the mailing list would be to just add the T5 specific
stuff to the end of the head section. 
>  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message