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

bug: updating a component causes instances to be displayed dismantled #3660

Closed
roberto-red opened this issue Sep 21, 2023 · 1 comment
Closed
Labels

Comments

@roberto-red
Copy link

roberto-red commented Sep 21, 2023

Steps To Reproduce

You have a master component and you already have several instances in the design. Now, you update the main component.

Expected behavior

The instances applied in the layout are updated correctly.

Actual behavior

I have a master component and I already have several instances in the design. When I updated the main component, the instances that were already applied to the design were dismounted. But it seems like a display problem because without having touched anything afterwards, everything has been put back in place, or if you double click on the text box, it goes back into place.

Screenshots or video

Master component:

imagen

Instances dismounted:

imagen

grabacion-de-pantalla-2023-09-13-a-las-91524_0EEv9qdY.mp4

Desktop (please complete the following information)

  • OS: macOS
  • Browser: Chrome (also observed on Firefox 117.0)

Smartphone (please complete the following information)

No response

Environment (please complete the following information)

This started to happen after a Penpot UI crash, like #3661 and #3662. We don't recall experiencing it before.

Frontend Stack Trace

No response

Backend Stack Trace

No response

Additional context

(I'm reporting this on behalf of a design colleague)

@roberto-red roberto-red changed the title bug: bug: updating a component causes instances to be displayed dismantled Sep 21, 2023
@madalenapmelo-kp
Copy link
Contributor

As per my comment on issue #3662, I'm closing this issue but please reopen it if this issue resurfaces!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants