[Webkit-unassigned] [Bug 200627] New: [iOS 13] App-registered system wide fonts unavailable to WKWebView/Safari
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Aug 12 07:04:12 PDT 2019
https://bugs.webkit.org/show_bug.cgi?id=200627
Bug ID: 200627
Summary: [iOS 13] App-registered system wide fonts unavailable
to WKWebView/Safari
Product: WebKit
Version: Safari Technology Preview
Hardware: iPhone / iPad
OS: iOS 12
Status: NEW
Severity: Normal
Priority: P2
Component: Text
Assignee: webkit-unassigned at lists.webkit.org
Reporter: jonathan at hacky.place
CC: mmaxfield at apple.com
Overview:
---------
A font registered for system use using iOS 13 CTFontManagerRegisterFonts* API can't be used in WKWebView.
Steps to reproduce:
-------------------
App A is a font provider, app B is a font consumer using a WKWebView.
1. In App A: add Fonts/Install Fonts privilege.
2. In App A: Register a custom font for system use using new CTFontManagerRegisterFontsWithAssetNames() API. For example, font 'Montez-Regular' from Google Fonts.
3. Run App A and register the font. Verify it appears on decvice in Settings.app->General->Fonts.
3. In app B: add Fonts/Use Installed Fonts privilege.
4. Display UIFontPickerViewController. Verify Montez font appears corectly and selects correct UIFontDescriptor with postscriptName 'Montez-Regular'.
5. Verify font can be applied to a UILabel.
6. Try to apply font in in html, e.g.:
`<body style="font-family: Montez-Regular;">hi</body>`
And load in a WKWebView as local file.
Actual Results:
---------------
Text is displayed using system default font.
In addition, attaching to Safari's web debugger shows the font doesn't appear in the list of available fonts in CSS properties editor.
Expected Results:
-----------------
Text will be displayed using custom font.
Build Date & Hardware:
----------------------
iOS 13.0 beta 5 (17A5556d) on iPad, iPhone (or simulator)
Additional Information:
-----------------------
Same behavior on Mobile Safari.
Submitted Feedback to Core Text team FB6958714
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190812/b78e4ba9/attachment.html>
More information about the webkit-unassigned
mailing list