1771322 - HTML text appears as wingdings

Status: RESOLVED WORKSFORME

(Core :: Layout: Text and Fonts, defect)

Description

[Zachary Clements]

Attachment: ffbug1.JPG

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:100.0) Gecko/20100101 Firefox/100.0

Steps to reproduce:

I have zero idea what happened or if its an issue in my settings or something that broke in an update but older sites and sites that use HTML text appears broke n

Actual results:

After updating a while back ceretain sites display text completley wrong

Expected results:

It should appear as basic HTML text. I have zero idea why the text appears as wingdings

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Core & HTML' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Emilio Cobos Álvarez (:emilio)]

Can you link to a site that reproduces the issue?

Comment 3

[Zachary Clements]

(In reply to Emilio Cobos Álvarez (:emilio) from comment #2)

Can you link to a site that reproduces the issue?

Here's some sites I use frequently that I see it on.

http://androidarts.com/ (homepage mostly, inidivudal articles are fine)
https://www.dreadxp.com/ (frotn page headers and article text)

Comment 4

[Emilio Cobos Álvarez (:emilio)]

Huh, I don't see this in any OS, does this happen for you in a clean profile? If not, mind checking your font settings and see if there's something unusual that could make this happen?

Comment 5

[Emilio Cobos Álvarez (:emilio)]

There were some recent related wingdings changes in bug 1756720 but there needs to be a setting that causes us to use that font as opposed to any other.

Comment 6

[Jonathan Kew [:jfkthame]]

Yeah, I'm pretty certain this means that the default font has been set to Wingdings in preferences. Check about:preferences#general, in the Language and Appearance section. If it doesn't show Wingdings as the "Default font" there, click the Advanced button to check the settings for the various possible writing systems; it's probably the Latin script setting that is relevant here.

Comment 7

[Zachary Clements]

(In reply to Jonathan Kew (:jfkthame) from comment #6)

Yeah, I'm pretty certain this means that the default font has been set to Wingdings in preferences. Check about:preferences#general, in the Language and Appearance section. If it doesn't show Wingdings as the "Default font" there, click the Advanced button to check the settings for the various possible writing systems; it's probably the Latin script setting that is relevant here.

Yep, that did the trick. The question still remains how it changed by its own.

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:dholbert, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 9

[Daniel Holbert [:dholbert]]

(In reply to Zachary Clements from comment #7)

Yep, that did the trick. The question still remains how it changed by its own.

That is indeed mysterious/odd.

Some things you could do to check / gather more information:

• could you let us know which of the various dropdowns was set to this font?

• Is it it displayed with the word "Default" in the dropdown (e.g. "Default (Wingdings)"), or is it just shown as "Wingdings"?

• Does the bug happen in a freshly-created Firefox profile? (See https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles#w_manage-profiles-when-firefox-is-open for how you can create a new Firefox profile -- essentially, just visit about:profiles, click the button to create one, and then click the button to "Launch profile in new browser". Then when you're done, you'll also want to click the "Set as default profile" button (on about:profiles) on your original Firefox profile, or else your newly-created one will automatically be the default profile that gets launched when you open Firefox.)

Comment 10

[Daniel Holbert [:dholbert]]

In any case: I think we can close this as WORKSFORME, since it turned out we were handling things properly according to the specified values in Firefox preferences.

(It is odd that this particular preference was set to something that the user did not intend; but I'm not sure we can't figure out more about what caused that without a time machine, or steps to reproduce the issue, or at least more reports of this happening for other folks. Answers to the questions in comment 9 would still be helpful, in case we do get more reports, though!)