-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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: elements are displayed dismantled #3662
Comments
Hi @roberto-red, Could you please confirm if you are still experiencing this behavior as well as the one reported on #3660? |
I can't reproduce it right now using Firefox 124.0 (aarch64) on macOS 14.3.1. But as I reported this on behalf of my design colleage @AnnaMassana, let's see if she can confirm it first-hand. |
Hi @roberto-red, As you haven't been able to reproduce this and we haven't received feedback from @AnnaMassana, I'm closing this issue as well as #3660 but if you continue to experience it please feel free to open a new one! |
Steps To Reproduce
You have several elements built with flex-layout, and you go to another place in the document and return to where you had the element.
Expected behavior
The design of the element remains as you left it.
Actual behavior
The element appears disassembled. 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
grabacion-de-pantalla-2023-09-13-a-las-134039_gg0NJfOH.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)
Host: https://design.penpot.app/
Version: 1.19
This started to happen after a Penpot UI crash, like #3660 and #3661. 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)
The underlying cause may be the same as #3660, but this one doesn't use components, just flex layout.
The text was updated successfully, but these errors were encountered: