<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><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> changed
<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [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;">Status</td>
<td>RESOLVED
</td>
<td>REOPENED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>INVALID
</td>
<td>---
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [GTK] Doesn't handle base64 encoded web fonts?"
href="https://bugs.webkit.org/show_bug.cgi?id=147296#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [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>(In reply to <a href="show_bug.cgi?id=147296#c6">comment #6</a>)
<span class="quote">> 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.</span >
Looks like this only works if we make the quirk depend on theverge.com, which makes sense. The URL that matters is the security context that actually runs the JavaScript. I think we have a few options here:
1. Give up on typekit fonts, at least on most pages.
2. Use OS X or the Chromium user agent by default (this is what we did before <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>).
3. Push for a fix in typekit.
To be honest, #1 is akin to just giving up on rendering the web properly. Obviously #3 would be ideal, but I don't really see the issue with #2, since that was the old behavior.
I'm also reopening this bug.</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>