Bug 189661

Summary: [GTK] WOFF2 font does not load in specific site: https://fortiguard.com
Product: WebKit Reporter: Reinhart Previano Koentjoro <reinhart_previano>
Component: TextAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: mcatanzaro, mmaxfield
Priority: P2    
Version: Other   
Hardware: PC   
OS: Linux   
Attachments:
Description Flags
Left: Firefox 62; Right: WebKitGTK+ 2.20.5 none

Reinhart Previano Koentjoro
Reported 2018-09-17 06:10:41 PDT
Created attachment 349884 [details] Left: Firefox 62; Right: WebKitGTK+ 2.20.5 Note: This report is originally submitted to webcompat.com, a community dedicated in resolving issues on websites which do not work on specific browsers. You can view the original thread at https://github.com/webcompat/web-bugs/issues/16736 which was forwarded to GNOME Web issue tracker at https://gitlab.gnome.org/GNOME/epiphany/issues/534. **URL**: https://fortiguard.com/faq/onlinescanner **Browser / Version**: Epiphany 3.28.1 (WebKitGTK+ 2.20.5) **Operating System**: Ubuntu **Tested Another Browser**: Yes **Problem type**: Design is broken **Description**: Lato webfont does not load **Steps to Reproduce**: 1. Visit the site. It is originally suspected that either the WOFF2 or `unicode-range` CSS `@font-face` support caused the issue. Not reproducible in Safari.
Attachments
Left: Firefox 62; Right: WebKitGTK+ 2.20.5 (261.98 KB, image/png)
2018-09-17 06:10 PDT, Reinhart Previano Koentjoro 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Reinhart Previano Koentjoro
Comment 1 2018-09-17 06:11:40 PDT
Actual result: the remote "Lato" webfont should be loaded.
Michael Catanzaro
Comment 2 2018-09-17 10:11:10 PDT
Ah, I tested both 2.22.0 and 2.20.1 and couldn't reproduce. Finally I remembered that Ubuntu has disabled the woff2 support. See https://bugs.launchpad.net/ubuntu/+source/woff2/+bug/1742743. P.S. Unrelated: 3.28.1 is a known-bad Epiphany release, the adblocker is a bit out of control breaking a bunch of websites. Beware! ;)
Note You need to log in before you can comment on or make changes to this bug.