<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#c12">Comment # 12</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: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#c11">comment #11</a>)
<span class="quote">> 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.</span >
I'm not going to insist the bug be open, but I think that just because there isn't a straight-forward fix today, doesn't mean that this isn't a real problem and that we shouldn't track it.</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>