Closed Bug 1865509 Opened 1 year ago Closed 1 year ago

font not rendering on sites but is rendering on Firefox UI

Categories

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

Firefox 119
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: u695318, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux aarch64; rv:109.0) Gecko/20100101 Firefox/119.0

Steps to reproduce:

On Fedora 39, running Sway (from Minimal install) using the native Firefox Fedora package, I noticed a friend's Discord username was not showing in Discord itself, the text being "𝕵𝖆𝖗𝖊𝖉" but was showing on Firefox's tab UI.

When I paste this text into the address bar and search for it, it is also visible in the address bar itself, but not in Google.

I tested the same on the native Chromium Fedora package, and it works as intended (visible on Chromium UI and in the website).

Actual results:

The text "𝕵𝖆𝖗𝖊𝖉" is visible in Firefox's UI elements, but not inside of websites (e.g. Google Search), while on Chromium the text is visible on both as intended.

Expected results:

For the text to be legible on both Firefox UI and inside websites (the fact it is visible in the Firefox UI, and on Chromium implies that it should not be an issue of a missing font on my end right?)

Component: Untriaged → Layout: Text and Fonts
Product: Firefox → Core

Do you have Enhanced Tracking Protection set to Strict (in about:preferences#privacy), or are you using Private Browsing mode? I suspect the math Fraktur characters (Unicode U+1D5xx) being used here require a font that is not part of the standard collection of fonts we expose to websites on Fedora, to limit font-based fingerprinting.

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

For more information, please visit BugBot documentation.

Flags: needinfo?(jwatt)

Hmm, the reporter's bugzilla account has been disabled for some reason (and their bugzilla account email address has been reset to be u[some-numerals]@disabled.tld as the domain name), so it looks like we're blocked from getting a response to comment 1.

Without more info, I think we can't make progress here; calling INCOMPLETE.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Flags: needinfo?(jwatt)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: