MHTML: fonts encoded as binary do not load |
|||
Issue descriptionChrome Version: 63.0.3239.84 (Official Build) (64-bit) OS: Linux What steps will reproduce the problem? (1) Load an MHTML file that contains a WOFF2 encoded with binary encoding What is the expected result? The font loads What happens instead? The font doesn't load. An error is reported in the console: OTS parsing error: Failed to convert WOFF 2.0 font to SFNT
,
Feb 6 2018
It looks like MHTMLParser is inserting an additional CRLF at the end of the resource. From rfc2046: The boundary delimiter MUST occur at the beginning of a line, i.e., following a CRLF, and the initial CRLF is considered to be attached to the boundary delimiter line rather than part of the preceding part. So given this snippet: --xxxboundaryxxx Content-Location: ... Content-Transfer-Encoding: binary binary --xxxboundaryxxx We should extract "binary" as the content, where as Chrome currently extracts "binary\r\n". This just happens to upset the font loader, but could be impacting other resource types.
,
Mar 28 2018
This is now fixed. See https://bugs.chromium.org/p/chromium/issues/detail?id=809806 |
|||
►
Sign in to add a comment |
|||
Comment 1 by dim...@chromium.org
, Jan 31 2018