<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [FreeType] Typekit fonts do not work"
href="https://bugs.webkit.org/show_bug.cgi?id=147296#c28">Comment # 28</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [FreeType] 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:mmaxfield@apple.com" title="Myles C. Maxfield <mmaxfield@apple.com>"> <span class="fn">Myles C. Maxfield</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=147296#c27">comment #27</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=147296#c25">comment #25</a>)
> > All of the features in the example work exactly as described, but the
> > sliders to toggle them are grayed out as if insensitive. So the page is
> > telling users WebKit does not support advanced font features, when in fact
> > they work fine.
>
> To clarify: in that example, you can click on the sliders and they actually
> work fine, same as in Firefox, even though they appear insensitive in WebKit.</span >
Yeah, I debugged that site a few weeks ago; they are doing naive UA detection along with a pre populated list of UAs that support font features. Unfortunately, they can't use @supports because we have had parsing support for the property for years (the properties just did nothing). Maybe they could use @supports with one of the newer properties I added, like font-variant-east-asian.</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>