Set X-UA-Compatible in ModuleTemplate for frontend editing
A customer of us uses Internet Explorer which is configured to use the compatibility mode by default.
<meta http-equiv="X-UA-Compatible" content="edge" />
This is output in the TYPO3 root frameset page via
In frontend editing, this root frameset - and thus the compat tag - is missing.
When editing content elements or page properties, the layout is broken.
The solution would be to add the render mode tag in
[!!!][TASK] Remove X-UA-Compatible from HTML of backend
Tested-by: TYPO3com <email@example.com>
Reviewed-by: Joerg Kummer <firstname.lastname@example.org>
Tested-by: Joerg Kummer <email@example.com>
Reviewed-by: Jürgen Heym <firstname.lastname@example.org>
Tested-by: Jürgen Heym <email@example.com>
Reviewed-by: Nicolai Schirawski <firstname.lastname@example.org>
Tested-by: Nicolai Schirawski <email@example.com>
Reviewed-by: Anja Leichsenring <firstname.lastname@example.org>
Tested-by: Anja Leichsenring <email@example.com>
#3 Updated by Wouter Wolters almost 4 years ago
I don't think setting this by default is a good idea.
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).
#5 Updated by Riccardo De Contardi over 2 years ago
- Status changed from New to Needs Feedback
A possible solution could be adding it only if you are logged in the backend, that is:
[globalVar = TSFE:beUserLogin = 1] page.meta.X-UA-Compatible = IE=edge page.meta.X-UA-Compatible.httpEquivalent = 1 [global]
I also guess that the new frontend editing does not need it at all.
Do you think it is sufficient to consider this issue closed? Thank you.