<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - [GTK] Doesn't handle base64 encoded web fonts?"
href="https://bugs.webkit.org/show_bug.cgi?id=147296">bug 147296</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>rego@igalia.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - [GTK] Doesn't handle base64 encoded web fonts?"
href="https://bugs.webkit.org/show_bug.cgi?id=147296#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - [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:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span></b>
<pre>The fonts are controlled by <a href="http://fonts.voxmedia.com/wvq7oai.js">http://fonts.voxmedia.com/wvq7oai.js</a> which seems to get them from either use.typekit.com or p.typekit.net or maybe both. We could try adding both of those to the quirks list and just use the existing quirk we have to add Chromium to the user agent.
Alternative: Adobe might fix it if somebody cares to complain. I visited <a href="https://typekit.com/">https://typekit.com/</a> and found at the bottom of the page:
Email: <a href="mailto:support@typekit.com">support@typekit.com</a>
Twitter: @typekit</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>