<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#c16">Comment # 16</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:cgarcia@igalia.com" title="Carlos Garcia Campos <cgarcia@igalia.com>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=147296#c2">comment #2</a>)
<span class="quote">> It looks like this is an issue with the user agent. The script that is
> serving fonts will not serve the proper fonts to us with our default
> user-agent. I have confirmed that the fonts load properly when using the
> user agent from Chromium in MiniBrowser "Mozilla/5.0 (X11; Linux x86_64)
> AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/43.0.2357.130
> Chrome/43.0.2357.130 Safari/537.36"</span >
I don't think UA string can be buggy (unless we don't follow the order or whatever), websites relying on UA strings and assuming there are only 3 browsers in the world are the buggy thing here. We don't fix anything in the browser engine, but work around buggy sites.
<span class="quote">> I think this is a regression from
> <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>, since reverting it locally
> seems to fix the issue. If I recall correctly (and I might not), this made
> our default user-agent string more like Safari and less like Chrome. Since
> there is no way we can add every single site that uses JavaScript-based CSS
> font libraries to the work-around list, perhaps we should use the Safari
> string as the work-around and the Chromey one as the default.</span >
This is the never ending story, we switched to Safari UA to fix a lot of sites trying to use chromium specific stuff. No matter what UA we use, there will always be broken sites. However, since we switched to Safari we have fewer problems, and I agree with Michael that switching back to chrome would make our quirk list longer.</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>