8270874: JFrame paint artifacts when dragged from standard monitor to HiDPI monitor

[mrserb]

Hi all,
This pull request contains a backport of commit 03473b4c from the openjdk/jdk repository.
The commit being backported was authored by Sergey Bylokhov on 18 Nov 2021 and was reviewed by Jayathirth D V.

The jdk_desktop tests are green on the system where the bug was reproduced.

Thanks!

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8270874: JFrame paint artifacts when dragged from standard monitor to HiDPI monitor

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17u-dev pull/38/head:pull/38
$ git checkout pull/38

Update a local copy of the PR:
$ git checkout pull/38
$ git pull https://git.openjdk.java.net/jdk17u-dev pull/38/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 38

View PR using the GUI difftool:
$ git pr show -t 38

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk17u-dev/pull/38.diff

[bridgekeeper]

👋 Welcome back serb! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

@mrserb This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8270874: JFrame paint artifacts when dragged from standard monitor to HiDPI monitor

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 00: Full (e3d6e855)

[mrserb]

/integrate

[openjdk]

Going to push as commit 493a78a.
Since your change was applied there have been 8 commits pushed to the master branch:

• f016e60: 8275610: C2: Object field load floats above its null check resulting in a segfault
• 3adb3dd: 8278099: two sun/security/pkcs11/Signature tests failed with AssertionError
• 38fdf4f: 8276623: JDK-8275650 accidentally pushed "out" file
• d30b6e4: 8277328: jdk/jshell/CommandCompletionTest.java failures on Windows
• 6aa60ac: 8277441: CompileQueue::add fails with assert(_last->next() == __null) failed: not last
• 15f2406: 8274714: Incorrect verifier protected access error message
• 4a38659: 8274658: ISO 4217 Amendment 170 Update
• 5287dae: 8274795: AArch64: avoid spilling and restoring r18 in macro assembler

Your commit was automatically rebased without conflicts.

[openjdk]

@mrserb Pushed as commit 493a78a.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.