<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - Typekit fonts do not work"
href="https://bugs.webkit.org/show_bug.cgi?id=147296#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - Typekit fonts do not work"
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>I don't agree. There's nothing we can do about this except to change our UA. We can't do it with a quirks list, since we would have to add every site that uses Typekit, and we can't do it by default, since sites would try to use Chrome-specific JS, so there's nothing we can do in WebKit, so no reason to keep the bug open. This isn't the first bug that can't be fixed client-side, and it won't be the last.
I've brought this to the attention of Jon, Apple's web evangelist. He may or may not be able to get the Typekit developers to fix this.</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>