You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Ville Virtanen (JIRA)" <ji...@apache.org> on 2010/12/05 21:43:11 UTC

[jira] Issue Comment Edited: (TAP5-648) Tapestry should be more careful about where, inside the , it adds new elements

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

Ville Virtanen edited comment on TAP5-648 at 12/5/10 3:42 PM:
--------------------------------------------------------------

As of 5.2.4 this is still broken, unfortunately. As MS states, the META tags that direct the rendering of IE must occur before css imports and such. Tapestry includes meta tags after the inclusion of javascript and css, which in this case is plain wrong. Just to make my point, this is again the spec: ".......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."

      was (Author: 9902468):
    As of 5.2.4 this is still broken, unfortunately. As MS states, the META tags that direct the rendering of IE must occur before css imports and such. Tapestry includes meta tags after the inclusion of javascript and css, which in this case is plain wrong.
  
> Tapestry should be more careful about where, inside the <head>, it adds new elements
> ------------------------------------------------------------------------------------
>
>                 Key: TAP5-648
>                 URL: https://issues.apache.org/jira/browse/TAP5-648
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.3
>            Reporter: Ville Virtanen
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.1.0.4
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.