Assistant font switches 'if' for 'fi' on iOS (Chrome and Safari)

[joeforce]

I'm having an issue using Assistant. It works perfectly on Desktop, even responsively in the browser. But when I browse my page is Safari or Chrome (iOS 10) it switches if to fi. For example, "different" becomes "dfiferent" and "diffuse" becomes "dfifuse". I saw a similar issue with Merriweather sans:

#184

Is there any workaround? Changing the typeface this late in the game is going to be a lot of work.

Here's a sample of the spelling issue:

Also, if you search the page for "dfi" it doesn't find it. The font is rendering wrong and the word is actually spelled correctly.

Thanks!

Joe

[davelab6]

Thanks @joeforce :) I filed an issue on the upstream repo :)

[georgiecel]

@joeforce I had the same problem then found this issue 😄 If you look at the Merriweather issue again, @davelab6 posted some workaround CSS that worked for me.

[miscavage]

+1

[davelab6]

This is just source sans pro, please use that until this is fixed

[aybmab]

Is there any eta on this?

@davelab6 what do you mean by just use sans pro? (apologies - I'm a font noob)

[davelab6]

The latin part of the family is (mean to be lol) an exact copy of Source Sans Pro. https://fonts.google.com/specimen/Source+Sans+Pro

[banbanbana]

Having issues on iOS but not desktop. Posted it on Twitter here:
https://twitter.com/awdoes/status/841306893800878082

[davelab6]

@laerm0 can be hotfixed like playfair was, swapping the components

[laerm0]

Okay, I'll take care of it today.

[laerm0]

The binaries we're serving are correct, both glyph and OT.

It also renders fine.

Am I missing something or is this no longer an issue?

[m4rc1e]

@laerm0 I'll take a look at this

[m4rc1e]

Ok, I've just tested the family on IOS using an Iphone SE, here's a jsbin

I can't replicate this issue:

@joeforce could you look at the Jsbin I just made on a device running IOS please?

The font was updated on the 2017-08-28, this may have solved the issue.

[m4rc1e]

The family contains Hebrew so this may an issue with some browsers and how they handle RTL scripts (just an assumption, not fact).

[davelab6]

@joeforce I'll close this as none of us can reproduce, but please reopen if you can still see this happening