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

Layout shift when closing the last column in a row #1268

Closed
mattrunyon opened this issue May 5, 2023 · 0 comments · Fixed by #2241
Closed

Layout shift when closing the last column in a row #1268

mattrunyon opened this issue May 5, 2023 · 0 comments · Fixed by #2241
Assignees
Labels
bug Something isn't working golden-layout
Milestone

Comments

@mattrunyon
Copy link
Collaborator

Description

This only appears to happen when you close or move the last item in the right-most column in a row. There is a vertical layout shift. Also, the drop zones can be temporarily wrong. They show correctly, but if there are many items in the left column and you try to drag the item from the right column into the left, it will sometimes drop in the completely wrong place (I think this happens on page reload specifically)

Steps to reproduce

  1. Create a multi-row layout. Put multiple columns in the last row (I think it works w/ middle row too)
  2. Put only 1 item in the last column of the row
  3. Close or drag the tab

Expected results

No layout shift

Actual results

Layout shift. If you drop the item back into its own column where it originally was and re-drag, no further layout shift occurs. Resizing and then dragging again causes layout shift

Additional details and attachments

The shift looks like it's around the height of the header, but not always. Sometimes the shift is up and other times down.

Screen.Recording.2023-05-05.at.6.03.12.PM.mov

Versions

  • Web UI Version: 0.37.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working golden-layout
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants