-
Notifications
You must be signed in to change notification settings - Fork 20
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 on path not working #139
Comments
Fix issue #139 Text on path broken after Generator update
I tried latest master and either I didn't set it up correctly or it's not working. watson bug 3833730 |
Looks like you have the commit before the last commit. I did not try with Crema but I get something meaningful:
|
while testing this, noticed another case of text on path not working correctly which seems different from original issue; I'm getting zero-bytes SVG files when exporting from one file. https://watsonexp.corp.adobe.com/#bug=3921139 |
Irina's test case 1 isn't rendering quite right for me as well:
Seems like the path points are positioned relative to the original doc, not the new asset bounds. |
Regarding Irina's second test case 2, two of the layers throw some JS errors in the console for me:
|
@mvujovic I can not reproduce it when generating the SVG for the whole document. It passes just fine. Maybe it happens when Crema tries to get the layer data of a specific layer. Then |
I'm exporting single layer, not entire document. |
can't reproduce the issue with 'ZZZZZ' in path anymore (not sure what 'fixed' it because I'm using the same build/same setup) but text is still not rendered correctly in SVG file; path seems correct (numbers, not 'z' anymore), but when previewing in Crema or Browser, text is not shown (same as screenshot mvujovic posted above) |
Remove the requirements for groups and shapes to have a unique id. Fixes...
With Generator 1.2.0 text on path is not working anymore. The segment coordinates were stored in number values but changed to objects with the number value as property and a unit as string.
This effects the test text-on-path
The text was updated successfully, but these errors were encountered: