http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692016-05-12T20:16:32ZTYPO3 ForgeTYPO3 Core - Bug #76166: Set X-UA-Compatible in ModuleTemplate for frontend editinghttp://forge.typo3.org/issues/76166?journal_id=3044132016-05-12T20:16:32ZWouter Wolterstypo3@wouterwolters.nl
<ul></ul><p>Can't you set the following header in the .htaccess?</p>
<p>Header set X-UA-Compatible "IE=edge"</p> TYPO3 Core - Bug #76166: Set X-UA-Compatible in ModuleTemplate for frontend editinghttp://forge.typo3.org/issues/76166?journal_id=3044192016-05-12T21:01:05ZChristian Weiske
<ul></ul><p>I can try that, or better the setting that's correct for nginx.</p>
<p>But that would only help me, and not others.</p> TYPO3 Core - Bug #76166: Set X-UA-Compatible in ModuleTemplate for frontend editinghttp://forge.typo3.org/issues/76166?journal_id=3044202016-05-12T21:47:47ZWouter Wolterstypo3@wouterwolters.nl
<ul></ul><p>I don't think setting this by default is a good idea.</p>
<p>From <a class="external" href="http://stackoverflow.com/questions/26346917/why-use-x-ua-compatible-ie-edge-anymore">http://stackoverflow.com/questions/26346917/why-use-x-ua-compatible-ie-edge-anymore</a></p>
<p>As David pointed out, outside of a page located in the "Local Intranet" zone, there is very little reason to include <meta http-equiv="X-UA-Compatible" content="IE=edge"> in your webpages, and absolutely no reason to include it in the HTML. (You should follow Microsoft's best practice recommendations and place it in your server config or site headers -- not in the HTML itself -- if you need it).</p> TYPO3 Core - Bug #76166: Set X-UA-Compatible in ModuleTemplate for frontend editinghttp://forge.typo3.org/issues/76166?journal_id=3044342016-05-13T09:34:28ZChristian Weiske
<ul></ul><p>If this is the official stance, then TYPO3 should completely drop this HTML head tag and not have it enabled in one place but not on the other.</p> TYPO3 Core - Bug #76166: Set X-UA-Compatible in ModuleTemplate for frontend editinghttp://forge.typo3.org/issues/76166?journal_id=3524802017-12-03T11:49:58ZRiccardo De Contardierredeco@gmail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li></ul><p>A possible solution could be adding it only if you are logged in the backend, that is:</p>
<pre>
[globalVar = TSFE:beUserLogin = 1]
page.meta.X-UA-Compatible = IE=edge
page.meta.X-UA-Compatible.httpEquivalent = 1
[global]
</pre>
<p>I also guess that the new frontend editing does not need it at all.</p>
<p>Do you think it is sufficient to consider this issue closed? Thank you.</p> TYPO3 Core - Bug #76166: Set X-UA-Compatible in ModuleTemplate for frontend editinghttp://forge.typo3.org/issues/76166?journal_id=3528632017-12-07T22:42:57ZChristian Weiske
<ul></ul><p>No, this issue is not closed. You posted a workaround that one could use after someone already stumbled over this bug.<br />The correct solution would be to add the fix to TYPO3 itself, so that the bug never appears at all.</p> TYPO3 Core - Bug #76166: Set X-UA-Compatible in ModuleTemplate for frontend editinghttp://forge.typo3.org/issues/76166?journal_id=3532612017-12-12T11:24:13ZRiccardo De Contardierredeco@gmail.com
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>New</i></li></ul> TYPO3 Core - Bug #76166: Set X-UA-Compatible in ModuleTemplate for frontend editinghttp://forge.typo3.org/issues/76166?journal_id=3891952018-10-25T11:49:15ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Sprint Focus</strong> set to <i>On Location Sprint</i></li></ul> TYPO3 Core - Bug #76166: Set X-UA-Compatible in ModuleTemplate for frontend editinghttp://forge.typo3.org/issues/76166?journal_id=3895392018-10-27T23:04:50ZGerrit Code Review
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Under Review</i></li></ul><p>Patch set 1 for branch <strong>master</strong> of project <strong>Packages/TYPO3.CMS</strong> has been pushed to the review server.<br />It is available at <a class="external" href="https://review.typo3.org/58744">https://review.typo3.org/58744</a></p> TYPO3 Core - Bug #76166: Set X-UA-Compatible in ModuleTemplate for frontend editinghttp://forge.typo3.org/issues/76166?journal_id=3896002018-10-28T12:30:04ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Status</strong> changed from <i>Under Review</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="[!!!][TASK] Remove X-UA-Compatible from HTML of backend Resolves: #76166 Releases: master Change..." href="http://forge.typo3.org/projects/typo3cms-core/repository/1749/revisions/9b222cebcedc31690c3a8666a8f8d0980b92a020">9b222cebcedc31690c3a8666a8f8d0980b92a020</a>.</p> TYPO3 Core - Bug #76166: Set X-UA-Compatible in ModuleTemplate for frontend editinghttp://forge.typo3.org/issues/76166?journal_id=4002922019-05-07T12:17:23ZBenni Mackbenni@typo3.org
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>