A Maximized Window is a Bad One #89
Labels
No Label
client
server
user made
L
M
S
XL
bug
bugfix
discussion
documentation
feature
maintenance
postponed
refactoring
wontfix
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: zdm/envoy#89
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It could be observed that JavaFX 15 seems to have a problem with maximized windows (it is unknown whether it was also previously there).
Whenever you maximize a Window, it can happen on certain OS (Ubuntu) that a new scene will not be loaded correctly:
While this does look not to bad at first, another thing is way worse:
While the components have changed their visual position, they are still expected to be where they should be. If you click randomly anywhere in the top area of the screenshot, there's a good chance you'll select one of the list elements.
Workaround: Move the application (or perform another action) to unmaximize it. Then everything should be back to normal behavior.
I have experienced a similar problem in the past, during which the new scene would be loaded at its default size, but the window wouldn't resize leaving a large amount of white space around the scene. This could also be resolved by resizing the window. I was using KDE on Debian at the time.
In fact, Mozilla Firefox has the same issue on my current setup, where it's starting maximized, but the tabs I load are displayed only inside of a certain area of the window.
As I am using KDE on Gentoo and you are using GNOME on Ubuntu, this appears to be a more general issue than just JavaFX being buggy.
I do remember though, that different results could be achieved by using
stage.sizeToScene()
insideSceneContext
.