8257414: Drag n Drop target area is wrong on high DPI systems

[omikhaltsova]

I'd like to backport JDK-8257414 to jdk15u for parity with jdk11u.
The original patch applied cleanly.
Tested manually.

---

Progress

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

Issue

• JDK-8257414: Drag n Drop target area is wrong on high DPI systems

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 21

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

Using diff file

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

[bridgekeeper]

👋 Welcome back omikhaltcova! 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]

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

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

8257414: Drag n Drop target area is wrong on high DPI systems

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 1 new commit pushed to the master branch:

• 7378892: 8248552: C2 crashes with SIGFPE due to division by zero

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 00: Full (9217b3a3)

[omikhaltsova]

/integrate

[openjdk]

@omikhaltsova
Your change (at version 9217b3a) is now ready to be sponsored by a Committer.

[yan-too]

/sponsor

[openjdk]

@yan-too @omikhaltsova Since your change was applied there has been 1 commit pushed to the master branch:

• 7378892: 8248552: C2 crashes with SIGFPE due to division by zero

Your commit was automatically rebased without conflicts.

Pushed as commit 44c196a.

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