<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] Doesn't handle base64 encoded web fonts?"
href="https://bugs.webkit.org/show_bug.cgi?id=147296#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] Doesn't handle base64 encoded web fonts?"
href="https://bugs.webkit.org/show_bug.cgi?id=147296">bug 147296</a>
from <span class="vcard"><a class="email" href="mailto:mrobinson@webkit.org" title="Martin Robinson <mrobinson@webkit.org>"> <span class="fn">Martin Robinson</span></a>
</span></b>
<pre>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 <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [GTK] Use a different user agent string depending on the site"
href="show_bug.cgi?id=132681">https://bugs.webkit.org/show_bug.cgi?id=132681</a>, 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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>