-
Notifications
You must be signed in to change notification settings - Fork 479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Font not working on macOS or iOS #614
Comments
Can you tell us what issue you're seeing on MacOS? Is it not displaying the characters? Is it displaying the wrong ones? If you could be a little more specific as to the issue it will help narrow down the cause. |
Visually, it just shows the missing character box. Aside from that, I'm not sure what exactly is happening. I'm viewing the font on a webpage, and the browser falls back onto another font (which presumably lacks those glyphs). Using the dev tools in Chrome/Safari (network tab), it appears to be happy, even showing a "preview" for the font (ABCDEFG– text). However, you can tell it's not loaded properly; I think I couldn't find a native way to load/view an OpenType file on macOS (on 10.15 at least), which I was hoping would give me more info about what's not working. |
Emoji font support isn't implemented in the library at the moment. This may be one reason. We'd have to check. |
I'm using opentype.js to modify the font files in
bootstrap-icons
(to strip out unused icons). It works on Windows and Android, but not on macOS or iOS. I suspected a WebKit error, but this occurs in Chrome on macOS. I also tried a WebKit browser on Windows to confirm, and it was fine.Possible Solution
I honestly have no clue where the issue even lies. Given the scope, this might not even be an issue with opentype.js, but there's obviously
something that's causing the outputted
woff
not to work, while the regular one does.Steps to Reproduce (for bugs)
I have a function that looks like this:
It deals with
woff
orwoff2
types, which is whatbootstrap-icons
exports. Even without modifying the underlying font data (as in the example), this issue occurs.Your Environment
Here's a zip with both the working unmodified version, and the "modified and broken" one.
I apologize for the lack of useful info; I genuinely don't know how I would go about debugging such a thing. Let me know if there's anything else I can do.
The text was updated successfully, but these errors were encountered: