Oct 13 2021 06:37 AM - edited Oct 13 2021 06:44 AM
Recently Edge started to be the Default File-Type-Association for .MHT Files.
But it seems the .MHT-File-Support is not implemented to Support true multipart/related MIME encapsulation of aggregate HTML documents but only certain style of "IE11-exported .mht Websites".
We have a ton of .mht Files, they are usually generated from MIME-formated-Mails. Default-Viewer was Internet Explorer 11 which renders those Files very well.
But Edge (I tested v93, v94, v95 Beta as well as v96 Dev) cannot render those .mht Files, shows only a "white Page".
Current Workaround: I configured Edge Policies to open locally stored .mht Files to open in Edge-IE-Mode. That works fine, so currently we can use this workaround as a solution.
But if Edge should be able to render .mht Files in a useful way itself then Edge has to support all styles of the MHTML-Standard. Wikipedia https://en.wikipedia.org/wiki/MHTML pointed me to a useful website where all styles of MHTML-Documents are listed with Samples, I mirrored those samples to my Webserver, URL: https://hitco.at/mht-test/ to quickly check those with Edge. These samples all don't work at all in Edge but work fine in IE or in Edge in IE-Mode.
So please have a look at this functionality, you cannot configure Edge as Default for .mht Files without really supporting the MHTML-Standard in a proper way!
Oct 25 2021 01:53 PM
@Gunnar Haslinger Thank you for sharing the repro files; a support case was opened.
As you noted, Edge/Chromium's support for MHT files today is limited in various ways (less liberal parsing than IE, web form controls are disabled in MHT content, more restrictive same-origin-policy behavior).
Today, the best way to ensure IE-style rendering of MHT files is to use IE Mode. As of Edge 94, that should happen by default for MHTML files unless they contain metadata suggesting that they were saved from Edge mode to start with[1].
Oct 25 2021 02:05 PM