[Webkit-unassigned] [Bug 147296] [GTK] Doesn't handle base64 encoded web fonts?

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Aug 15 16:28:10 PDT 2015


https://bugs.webkit.org/show_bug.cgi?id=147296

--- Comment #2 from Martin Robinson <mrobinson at webkit.org> ---
It looks like this is an issue with the user agent. The script that is serving fonts will not serve the proper fonts to us with our default user-agent. I have confirmed that the fonts load properly when using the user agent from Chromium in MiniBrowser "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/43.0.2357.130 Chrome/43.0.2357.130 Safari/537.36"

I think this is a regression from https://bugs.webkit.org/show_bug.cgi?id=132681, since reverting it locally seems to fix the issue. If I recall correctly (and I might not), this made our default user-agent string more like Safari and less like Chrome. Since there is no way we can add every single site that uses JavaScript-based CSS font libraries to the work-around list, perhaps we should use the Safari string as the work-around and the Chromey one as the default.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150815/817e4bfc/attachment.html>


More information about the webkit-unassigned mailing list