Changes pushed with changeset a298f27945aafc8282c103c90916d4c7ca57c82f
Push date [To Local]
ChangesetPatch author — Commit message
Wed Nov 22 13:58:57 2017 +0000
5758facf358ba61b7bebb63d9b8e873f30f33124Jonathan Kew — Bug 1412090 - patch 4 - Also adopt the ContentParent::NotifyUpdatedFonts method on macOS, so that only the parent process needs to register with CFNotificationCenter for font-changed notifications. r=lsalzman a=gchang
5edf5a792dc37f502452fc103fbdf490b7b6874bJonathan Kew — Bug 1412090 - patch 3 - Check the sandbox policy to verify font files will be readable by the content process before including them in the system font list. r=gps a=gchang
a298f27945aafc8282c103c90916d4c7ca57c82fJonathan Kew — Bug 1412090 - patch 2.1 - Work around FcNameParse bug in fontconfig versions around 2.11.0, by escaping any leading space in the encoded charset element. r=lsalzman a=gchang
a9f13ba650d2121ba8e519779a04e43815df0f7cJonathan Kew — Bug 1412090 - patch 2 - Rework the fontconfig-based platform font list implementation to pass the list of available font patterns from chrome to content, instead of letting the content process get it directly from fontconfig. r=lsalzman a=gchang
bfe05205f198cf7e4aac88e515725ee3fc394023Jonathan Kew — Bug 1412090 - patch 1 - Wrap the font family record used to pass font info from chrome to content on macOS in a union, in preparation for using the same mechanism with a different type of font record on Linux. (No functional change here, just the added union type and some renamings from 'font family list' to 'font list' to be more generic.) r=lsalzman a=gchang