You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/12/06 19:15:12 UTC
[jira] Created: (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
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
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.
[jira] [Commented] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065628#comment-13065628 ]
Howard M. Lewis Ship commented on TAP5-1366:
--------------------------------------------
So, now, whatever new elements Tapestry inserts go just before the first existing such element, or at the end of the <head>. Keeping the rest valid is now up to the template that renders <head> being valid.
> 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
[jira] [Commented] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065656#comment-13065656 ]
Hudson commented on TAP5-1366:
------------------------------
Integrated in tapestry-trunk-freestyle #417 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/417/])
TAP5-1366: Add new <style> tag before first existing <style> tag, or at bottom of <head>
TAP5-1366: Refactoring and insert <meta> just before existing <meta>, or at end of <head>
TAP5-1366: Add new method to insert an element before an existing element
TAP5-1366: Add missing documentation
TAP5-1366: Minor documentation improvements and reformats
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1146929
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/org/apache/tapestry5/internal/services/existing_head_used_if_present.txt
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DocumentLinkerImpl.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1146928
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DocumentLinkerImpl.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1146926
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/dom/Element.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1146925
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/dom/Element.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1146924
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DocumentLinkerImpl.java
> 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
[jira] [Updated] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Ville Virtanen (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1366:
---------------------------------------
Affects Version/s: (was: 5.2.4)
(was: 5.2.3)
(was: 5.2.2)
(was: 5.2.1)
(was: 5.2.0)
(was: 5.1.0.5)
(was: 5.1.0.4)
(was: 5.1.0.3)
(was: 5.1.0.2)
(was: 5.1.0.1)
(was: 5.1.0.0)
5.2
5.3
> 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
>
> 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
[jira] [Commented] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Bob Harner (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Ville Virtanen (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Bob Harner (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065656#comment-13065656 ]
Hudson commented on TAP5-1366:
------------------------------
Integrated in tapestry-trunk-freestyle #417 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/417/])
TAP5-1366: Add new <style> tag before first existing <style> tag, or at bottom of <head>
TAP5-1366: Refactoring and insert <meta> just before existing <meta>, or at end of <head>
TAP5-1366: Add new method to insert an element before an existing element
TAP5-1366: Add missing documentation
TAP5-1366: Minor documentation improvements and reformats
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1146929
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/org/apache/tapestry5/internal/services/existing_head_used_if_present.txt
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DocumentLinkerImpl.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1146928
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DocumentLinkerImpl.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1146926
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/dom/Element.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1146925
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/dom/Element.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1146924
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DocumentLinkerImpl.java
> 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
[jira] [Closed] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1366.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3
> 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
[jira] [Commented] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065628#comment-13065628 ]
Howard M. Lewis Ship commented on TAP5-1366:
--------------------------------------------
So, now, whatever new elements Tapestry inserts go just before the first existing such element, or at the end of the <head>. Keeping the rest valid is now up to the template that renders <head> being valid.
> 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
[jira] [Closed] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1366.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3
> 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
[jira] [Updated] (TAP5-1366) Tapestry must honor the position of
added tags in the relative to the tags, for IE compatibility
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1366:
---------------------------------------
Affects Version/s: (was: 5.2.4)
(was: 5.2.3)
(was: 5.2.2)
(was: 5.2.1)
(was: 5.2.0)
(was: 5.1.0.5)
(was: 5.1.0.4)
(was: 5.1.0.3)
(was: 5.1.0.2)
(was: 5.1.0.1)
(was: 5.1.0.0)
5.2
5.3
> 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
>
> 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