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
Text - Rendering differences when text justified with strikethrough #2449
Comments
Did you debug the cause? So i'm amazed nodecanvas has problem with it. |
sorry @asturur haven't had a chance to work on this at all. Still one of the things I need to look into. |
I'm not good with nodejs + fabric yet. I need a simple js file that contains: In the middle i will add the code i need to debug. Or something that will start simple webserver that outputs the png in my broeser instead of putting in the folder. If i have a tool like this i can start. I have so many issues to take care of that i always postpone node. |
@asturur I have a simple web debugger, but it is unfortunately strongly tied to our application (we store information about shapes very differently for legacy reasons, etc). Unfortunately its my last week at this job, and I too (like kagnax) am starting a new job elsewhere. All that said, I will try to setup a small application for you based on JSON export that can re-create this experiment. |
Hey @asturur, I cannot seem to replicate this in the Kitchensink (http://fabricjs.com/kitchensink). Text that has strike-through and is justified does not render the same in the kitchensink as it does in my application. I have setup a small debug renderer you can use, the gist is available here: It basically allows you to pass in JSON, and renders it. It needs some work (dynamic sizing, etc) but should be a good start. I use something similar for our internal application. |
@asturur I am not sure if the Kitchensink version changed, but today the results are different. Try the following JSON:
|
nodecanvas2 seems to solve this |
I am just rigorously testing my application for differences between client and server side rendering, and I came across one right now.
When rendered in the browser, it looks correct:
The same, when rendered in node-canvas:
I will be debugging this later on, but if anyone has any ideas on what it could be, any help would be appreciated.
The text was updated successfully, but these errors were encountered: