Workaround for CefBrowserWr.setBounds Incorrect Scaling Issue After M… #488
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…onitor Change Updated setBounds to use SwingUtilities.invokeLater to ensure that resizing is executed on the Swing Event Dispatch Thread (EDT) This issue frequently occurs when moving a CefBrowser component between monitors with different DPI settings. Specifically, when setBounds is invoked, it continues to use the scale factor from the previous monitor, leading to incorrect scaling in Swing-based Java applications.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…onitor Change
Updated setBounds to use SwingUtilities.invokeLater to ensure that resizing is executed on the Swing Event Dispatch Thread (EDT)
This issue frequently occurs when moving a CefBrowser component between monitors with different DPI settings. Specifically, when setBounds is invoked, it continues to use the scale factor from the previous monitor, leading to incorrect scaling in Swing-based Java applications.
If you have suggestions for a better approach, I am open to updating this pull request accordingly.
issue #438``