Bug 167798

Summary: WebKit Nightly fails to shape NotoSansArabic variation font
Product: WebKit Reporter: Dominik Röttsches (drott) <d-r>
Component: TextAssignee: Nobody <webkit-unassigned>
Status: RESOLVED MOVED    
Severity: Normal CC: bfulgham, mmaxfield, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
index.html with reproduction and NotoSansArabic font
none
Actual result in WebKit nightly
none
Expected result, chrome dev version none

Dominik Röttsches (drott)
Reported 2017-02-03 10:11:38 PST
Created attachment 300540 [details] index.html with reproduction and NotoSansArabic font Using WebKit Nightly r211623 and the reproduction attached to this bug, WebKit does not shape the experimental Noto Sans Arabic font correctly. The arabic test string appears disconnected and variation settings are not applied.
Attachments
index.html with reproduction and NotoSansArabic font (288.39 KB, application/zip)
2017-02-03 10:11 PST, Dominik Röttsches (drott)
no flags
Actual result in WebKit nightly (124.93 KB, image/png)
2017-02-03 10:13 PST, Dominik Röttsches (drott)
no flags
Expected result, chrome dev version (107.33 KB, image/png)
2017-02-03 10:13 PST, Dominik Röttsches (drott)
no flags
Dominik Röttsches (drott)
Comment 1 2017-02-03 10:13:16 PST
Created attachment 300541 [details] Actual result in WebKit nightly
Dominik Röttsches (drott)
Comment 2 2017-02-03 10:13:50 PST
Created attachment 300542 [details] Expected result, chrome dev version
Dominik Röttsches (drott)
Comment 3 2017-02-03 10:14:39 PST
One correction to the initial report: WebKit nightly does apply the variation axis values, but does not shape the Arabic right.
Myles C. Maxfield
Comment 4 2017-02-03 10:29:32 PST
Reproduces in a native test app using raw CoreText. Off to that team.
Radar WebKit Bug Importer
Comment 5 2017-02-03 10:29:54 PST
Brent Fulgham
Comment 6 2022-02-10 19:41:43 PST
The fix for this issue was needed outside the WebKit project, therefore this is being resolved as 'Moved'. This should now be fixed in shipping software.
Note You need to log in before you can comment on or make changes to this bug.