Closed Bug 1535051 Opened 7 years ago Closed 7 years ago

User-selected monospace font not used for remote resources

Categories

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

65 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1512731

People

(Reporter: mqudsi, Unassigned)

Details

Attachments

(6 files, 1 obsolete file)

Attached file test.html

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

Steps to reproduce:

  1. Set a custom monospace font and allow pages to choose their own fonts (see screenshot)
  2. Load the test page both locally (via a file:/// url) and remotely (via a local webserver)

Actual results:

The user-selected custom font for unstyled <pre> tags or substituted where "font-family: monospace;" is used where applicable for the page loaded via file:/// (see screenshot) but not for the page loaded over http (see screenshot).

This also, oddly, affects the source viewer (see screenshot).

Expected results:

The user-selected custom font should have been used instead of font-family: monospace; and for <pre> tags unassociated with any style in both cases.

Attached image local correct.png (obsolete) —
Attached image remote incorrect.png
Component: Untriaged → Layout: Text and Fonts
Product: Firefox → Core

The images in comment 2 and comment 3 look identical to me -- did the wrong file get attached in one case, possibly?

Flags: needinfo?(mqudsi)
Attached image local correct.png

My apologies. Resubmitted.

Attachment #9050696 - Attachment is obsolete: true
Flags: needinfo?(mqudsi)

Thanks. Just to confirm, if you load your test file (attachment 9050694 [details]) from here in bugzilla, rather than via a local webserver, does that make any difference?

It's also rendered in Courier New rather than my chosen font.

I think there is a bigger underlying issue. Just filed #1535290

It sounds like this was a result of bug 1512731 blocking the use of your chosen font; with that fixed (e.g. in current Nightly), is there still an issue here or can we resolve this as being the same underlying problem?

I think we're good here! :)1

Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: