UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.9) Gecko/20100101 Goanna/2.1 Firefox/38.9 PaleMoon/26.4.0

Example URL:
attached mht file

Steps to reproduce the problem:
1. create a mhtml file containing non-ascii characters in a 8bit content-encoding
2. try to open it in any chromium-based browser

What is the expected behavior?
show mht file contents as other browsers do

What went wrong?
empty window

Does it occur on multiple sites: Yes

Is it a problem with a plugin? N/A 

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 57.0.2987.0 (Developer Build) (32-bit)  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

This problem is specific to 8bit and chromium engine.
Firefox (mozarchive and unmht): Works
Internet explorer 8-11: Works
Opera 15+: Fail
Cent browser: Fail
Chromium dev build: Fail

Will attach specially crafted mht file which showcases the problem.
Basically, if one of mhtml multi-parts is in 8bit encoding and has non-ascii symbols, then chromium-based browsers do not display it at all.
If 8bit encoding definition is replaced by 'binary' then it works.

Seeing other browsers working with 8bit, I'd like chromium engine to do the same. I have a program written for me which outputs mhtml in this format and these files are forcing me to use firefox which I really don't like to do.

Also, I'd be grateful if anyone tech-savvy can explain to me the difference between 'binary' and '8bit' encodings and why chromium didn't support it from start. Everything I found in google just points out that both of these encodings are 'as is' and need to be decoded by browser.

 

Deleted: testmht.mht 607 bytes

testmht.mht 607 bytes Download