Skip to content
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

Path error when editing an externally imported svg icon #971

Closed
soultipsy opened this issue May 24, 2021 · 4 comments · Fixed by #972
Closed

Path error when editing an externally imported svg icon #971

soultipsy opened this issue May 24, 2021 · 4 comments · Fixed by #972
Assignees
Labels
Milestone

Comments

@soultipsy
Copy link
Contributor

Describe the bug
When complex SVG paths are pasted externally, anchor points become stuck, incorrectly merged, incorrectly positioned, and jumbled path lines appear.

To Reproduce
Steps to reproduce the behavior:

Import any complex svg icon from outside
Go to the layer and double-click to edit the svg path
The svg path appears to be incorrectly merged and cannot be recovered

Expected behavior
The svg path should remain as it is, and there should be no incorrect merges or fills.

Screenshots
2021-05-24-15-13-39

Desktop (please complete the following information):

OS: Windows
Browser : Microsoft Edge & Firefox
Version : 91.0.864.33 & 88.0.1

Environment (please complete the following information):

SAAS( https://design.penpot.app

@soultipsy soultipsy added the bug label May 24, 2021
@elhombretecla
Copy link
Contributor

Hi @soultipsy!

Could you send to us this icon SVG to do some test? This error is unknown to us.
Our email is info@penpot.app

Thank you!

@soultipsy
Copy link
Contributor Author

soultipsy commented May 24, 2021

Ok, @elhombretecla I have sent you guys an email. In fact, when I tried to edit the demo file of the penpot-design system, something similar happened, I've attached a screenshot to the email, please check it.

@soultipsy soultipsy reopened this May 24, 2021
@Alotor
Copy link
Member

Alotor commented May 24, 2021

Thanks @soultipsy we've solved the issue in our local environment. We have a release planned for this week and will be fixed by then.
Cheers,

@Alotor Alotor self-assigned this May 24, 2021
@Alotor Alotor added this to the 1.6.0-alpha milestone May 24, 2021
@Alotor Alotor mentioned this issue May 24, 2021
@elhombretecla
Copy link
Contributor

@niwinz niwinz closed this as completed Jun 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants