-
Notifications
You must be signed in to change notification settings - Fork 87
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
External fonts don't work - Upgrade to PhantomJS 2 #27
Comments
Probably a page load listener should be added before rendering. If it is possible for you please check if you can fix it, otherwise I will try to fix it as soon as I'm free. |
I'm looking to add support for the load event right now in a fork. Will submit a PR when done. https://github.com/newworldcode/svgexport |
That's great, thanks! |
Well.. What a waste of time that was.. It just turns out that it doesn't support fonts very well.. Need to update to PhantomJS 2.0 http://stackoverflow.com/questions/23404658/how-can-i-use-google-web-fonts-with-phantomjs |
Working on an update. |
💥 Got Phantom 2.0 working and fonts are fixed. Will be submitting a PR once the tests are fixed. |
@davemackintosh Thanks, I have been resisting to upgrade to phantomjs 2.0 for a while, but it seems that this time I can not! Please give me just few days. |
How come you've resisted updating? |
The main phantomjs npm package is not upgraded to v2 yet and this issue is still open. I just checked the phantomjs2 npm package, it does not support Windows yet. I will use it in an alpha version, because otherwise svgexport won't be usable in Windows. |
Looks like that issue has been closed and updated, I think this PR is outdated now that 2.1 is out. I will revisit in the next few days to update the PR. |
@davemackintosh Thanks, I appreciate your help. It seems that the package name is also changed to phantomjs-prebuilt. |
If you're using web fonts, from say Google Fonts they won't appear because there is no wait for resources to finish loading before rendering the image.
Is there any fix for this?
The text was updated successfully, but these errors were encountered: