[
https://issues.apache.org/jira/browse/TAP5-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ville Virtanen updated TAP5-1366:
---------------------------------
Description:
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.
was:
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.
> 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.2.0, 5.2.1, 5.2.2, 5.2.3, 5.2.4, 5.1.0.0, 5.1.0.1,
> 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5
> Reporter: Ville Virtanen
> Assignee: Howard M. Lewis Ship
>
> 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
