Loading…
21
My custom icon font broke in Safari because of one missing glyph name
Spent most of Saturday night fighting with a hand-coded icon font I built for a client's dashboard, and it looked perfect in Chrome and Firefox. Loaded it up in Safari on my old iPad and half the icons turned into empty boxes, 14 out of 22 just gone. Turns out I had named one glyph with a capital letter in the middle, like arrowUp instead of arrow-up, and Safari was quietly choking on the whole font file instead of just skipping that one. I renamed it, rebuilt the woff2 with fonttools, and everything popped back in. Cost me about 4 hours and a cold pizza to find a fix that took 30 seconds. If you hand-build your own icon sets, do you test in Safari first or just trust the browser you use every day?
0 comments
Log in to join the discussion
Log In0 Comments
No comments yet
Be the first to share your thoughts on this discussion.