HTML files attached showing text improperly displayed
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
People
(Reporter: rlewis-0w, Unassigned)
Details
(Keywords: parity-chrome)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0
Steps to reproduce:
Display HTML file
Actual results:
See "Sample Files.zip" attached. File to display in Firefox is "ad65632.html". File displayed as shown in file "Firefox.jpg."
Expected results:
The file should display as in file "Chrome.jpg."
Maybe the problem is in my Windows 10 configuration or my Firefox configuration. I wish I would know how to send you a dump of my Windows 10 configuration settings and Firefox configuration settings. Maybe you would be able to figure what needs to change.
The bug aspect of this report is would be good for Firefox default settings to display the file more reasonably.
Although similar issues have been reported, this report provides a specific file, a "does display" snapshot, and a "should display" snapshot.
Comment 2•6 years ago
|
||
Your HTML file lacks all headers. In the case of a local file, this leaves the browser to guess the character encoding. Firefox 64 doesn't get it right, but the latest Nightly does.
Until Firefox 66 is released, you can manually switch the encoding to Unicode as follows:
- Right-click the ≡ Menu button in the corner of the window and choose Customize…
- Drag the "Text Encoding" icon onto the navigation toolbar, then click the "Done" button.
- Click the "Text Encoding" button and choose "Unicode" from the list. This option is unavailable when the server specifies the character encoding.
The "vineleafboldne" ornamental Wingdings character will still not display. For reasons why, see bug 90643 and its list of duplicates. Use the Unicode symbol U+1F65E instead.
Comment 3•6 years ago
|
||
I've attached a fixed version of your page that displays correctly in Firefox 64.
- added headers
- removed " from style attribute values
- Replaced Wingdings characters with 🙞
Such good news that fixed in Firefox 66. The workaround for text encoding displayed the file much better. In this case, appropriate for me to contact the website that originates these files that don't display correctly in Firefox. I can ask them to include the headers to specify the encoding.
Thank you for getting my issue solved and resolved so quickly. I am amazed that the answer came in minutes. And the answer is clear and easy to understand.
Description
•