When I'm editing a jellycut on my iPad, and I've opened the documentation in a new window and then dismissed it, the contents of the toolbar are crammed into the horizontal space that the sidebar would usually cover, rather than being spread out across the screen like they usually are.
When in portrait mode, the toolbar contents are crammed into the horizontal space that the sidebar would usually cover. In landscape mode, the toolbar contents are stuck in the horizontal space that the editor window occupied while the docs were open.
To Reproduce
Open up a jellycut in the editor.
Open the documentation from the toolbar.
Tap the macwindow.badge.plus button in the upper left corner to open the docs in a new window.
Tap "Dismiss" on the documentation window.
Observe that the toolbar contents are crammed to the area that the sidebar would usually cover.
Expected behavior
The toolbar contents should fill the width of the screen at all times while the toolbar is visible.
Screenshots
Information
Device: iPad (7th generation)
OS: iPadOS 14.4.1
Jellycuts Version: 0.9(20)
Additional context
You said on the Discord server that you've encountered this as well in your own tests; I'm just leaving this here as an issue for the bug tracker.
Describe the bug
When I'm editing a jellycut on my iPad, and I've opened the documentation in a new window and then dismissed it, the contents of the toolbar are crammed into the horizontal space that the sidebar would usually cover, rather than being spread out across the screen like they usually are.
When in portrait mode, the toolbar contents are crammed into the horizontal space that the sidebar would usually cover. In landscape mode, the toolbar contents are stuck in the horizontal space that the editor window occupied while the docs were open.
To Reproduce
Expected behavior
The toolbar contents should fill the width of the screen at all times while the toolbar is visible.
Screenshots
Information
Additional context
You said on the Discord server that you've encountered this as well in your own tests; I'm just leaving this here as an issue for the bug tracker.