[Webkit-unassigned] [Bug 147296] Typekit fonts do not work

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Nov 17 14:13:49 PST 2015


--- Comment #20 from Michael Catanzaro <mcatanzaro at igalia.com> ---
Martin, besides Typekit, what other framework are you aware of that has problems with our UA? I know we talked about jQuery's problems with touch detection, but to be clear, that is not a UA issue.

(In reply to comment #14)
> What is Epiphany's user agent string?

It's a *BIG* problem if there's no way to detect font format support asides from UA parsing. Relying on our UA means it will *ALWAYS* be broken for some browsers. Anyway, for me:

Mozilla/5.0 (Fedora; Linux x86_64) AppleWebKit/602.1 (KHTML, like Gecko) Version/8.0 Safari/602.1 Epiphany/3.18.0

But please don't look for "Epiphany" as you'll fix one browser but leave basically other WebKit browsers broken; just look for AppleWebKit and the version number there....


Note that we patch WebKit to put the distro branding in a different place than where it goes by default (the Ubuntu location in Martin's UA), since we want it to match where it goes in Firefox. This, too, breaks sites (Google Calendar assumes Linux without X11 means phone, and turns into crap); we can't win....

The other big problem I'm noticing is that sites are starting to check the architecture to decide whether to show a mobile site; they seem armv7l and think "oh it's ARM, must be a phone." Sucks for you if you're using an ARM-based desktop, but the only thing we can do is fake our arch in the UA... and then that gives wrong results if you ARE using a phone.

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/20151117/c77c2978/attachment.html>

More information about the webkit-unassigned mailing list