[Webkit-unassigned] [Bug 147296] [GTK] Doesn't handle base64 encoded web fonts?

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=147296

Martin Robinson <mrobinson at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |---

--- Comment #7 from Martin Robinson <mrobinson at webkit.org> ---
(In reply to comment #6)
> The fonts are controlled by http://fonts.voxmedia.com/wvq7oai.js 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.

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 https://bugs.webkit.org/show_bug.cgi?id=132681).
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150822/6984f226/attachment-0001.html>