Hi Vernon,
Thank you for the report.
Chrome on Mac OS X does not use FreeType, but as you said, it's possible that the way composite glyphs are handled by ttautohint can get in the way of rendering those glyphs by Chrome on Mac OS X for some reason. One possibility is that
Skia (2D graphics library used across platforms by Chrome) chokes on some of those glyphs. In the past, we've observed something similar to what you observed (part wiped out, missing stems, etc) for some fonts on Mac, Windows and Linux and all of them were attributed to Skia.
Having said that, I've tried your web page with Chrome 26.0.1410.5 dev channel and I don't see any problem ('i', 'ff' and 'f'). I may have missed what you see and I'm attaching a screenshot for you to take a look at. I also tried Chrome canary (nightly build) 27.0.1454.0 and didn't see any problem, either.
It's possible that Skia had a problem with fonts auto-hinted by ttautohint, but the issue has been fixed since. What version of Chrome do you have?
Jungshik