8343977: Convert java/awt/TextArea/TextAreaCursorTest/HoveringAndDraggingTest to main

[TejeshR13]

The test is supposed to be problem listed on macos & Linux but the Problem list points to the .java file instead of the .html file.
Hence converting java/awt/TextArea/TextAreaCursorTest/HoveringAndDraggingTest to main which would automatically resolve the issue.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8343977: Convert java/awt/TextArea/TextAreaCursorTest/HoveringAndDraggingTest to main (Bug - P4)

Reviewers

• Alisen Chung (@alisenchung - Committer) 🔄 Re-review required (review applies to c7e6339f)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22026/head:pull/22026
$ git checkout pull/22026

Update a local copy of the PR:
$ git checkout pull/22026
$ git pull https://git.openjdk.org/jdk.git pull/22026/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 22026

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22026.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back tr! 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 change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

@TejeshR13 The following label will be automatically applied to this pull request:

• client

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[alisenchung]

On macos I see no scroll buttons so the test instructions are slightly inaccurate. Are there any plans to fix the issue of mouse cursor changing when dragging onto different components? What should be expected behavior here? What happens on native applications?

[mlbridge]

Webrevs

• 04: Full - Incremental (d2d8c649)
• 03: Full - Incremental (4057be1b)
• 02: Full - Incremental (c7e6339f)
• 01: Full - Incremental (30e7f98e)
• 00: Full (4a03f25f)

[DamonGuy]

Still consider the minor suggestions remaining, but the test works and it's instructions look good.

[kumarabhi006]

Tested on win11 system and it didn't work as expected while dragging mouse from text_box to any other component. Mouse cursor changed to default Arrow style as soon as mouse is dragged out of text box.
However the applet version of test is working as expected on windows.

No issues on Ubuntu_22.04 system.

[TejeshR13]

Tested on win11 system and it didn't work as expected while dragging mouse from text_box to any other component. Mouse cursor changed to default Arrow style as soon as mouse is dragged out of text box. However the applet version of test is working as expected on windows.

No issues on Ubuntu_22.04 system.

Yes, looks like its not consistent. I see the issue happens when we are using JPassFailJFrame, without it there is no issue. Will get back on this.

[DamonGuy]

I also tried running on win11 after Abhishek's find. Looks like he's right. Looking at your changes, I don't see a setCursor anywhere, so it probably has something to do with PassFailJFrame. The only other difference in your changes I see is the StringBuilder, but that seems unlikely to be the cause.

[bridgekeeper]

@TejeshR13 This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[bridgekeeper]

@TejeshR13 This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.