Closed Bug 1296106 Opened 8 years ago Closed 8 years ago

Gracefully fall back when Osaka-Mono font is not available

Categories

(Firefox :: Shell Integration, defect)

Product:
Firefox
Component:
Shell Integration
Version:
47 Branch
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1283573

People

(Reporter: lmandel, Unassigned)

Details

Issue reported by Apple.

Please communicate with Firefox developers about the following problem regarding UI font usage in their app (Firefox 47 as of now):

The code attempts to use Osaka-Mono as the default fixed-pitch Japanese font, but Osaka-Mono is no longer available by default in the system, it becomes a downloadable font that may not may not exist. When it doesn’t exist and the application requests it, a system dialog for downloading the font will be triggered. To query the existence without triggering such a dialog, set kCTFontEnabledAttribute to kCFBooleanTrue in the font query send to CoreText. It is suggested that the app should gracefully fallback to a different font when Osaka-Mono doesn’t exist.

https://github.com/mozilla/gecko-dev/blob/master/modules/libpref/init/all.js#L3547
Markus, can you look at this issue reported by Apple?
Flags: needinfo?(mstange)
We already fixed it in bug 1283573.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(mstange)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.