8296632: Write a test to verify the content change of TextArea sends TextEvent

[Rudometov]

Backport for JDK-8296632 Write a test to verify the content change of TextArea sends TextEvent https://git.openjdk.org/jdk/commit/59a308b9d0546471566b11f62ef9bdc169ca0b95

Clean Backport.
New test, low risk.
Test passes during manual run: make run-test TEST="test/jdk/java/awt/event/ComponentEvent/TextAreaTextEventTest.java"

---

Progress

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

Issue

• JDK-8296632: Write a test to verify the content change of TextArea sends TextEvent

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev pull/903/head:pull/903
$ git checkout pull/903

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 903

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/903.diff

[bridgekeeper]

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

@Rudometov 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:

8296632: Write a test to verify the content change of TextArea sends TextEvent

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 2 new commits pushed to the master branch:

• 728dc4d: 8296083: javax/swing/JTree/6263446/bug6263446.java fails intermittently on a VM
• 1c13d7e: 8290839: jdk/jfr/event/compiler/TestJitRestart.java failed with "RuntimeException: No JIT restart event found: expected true, was false"

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 (fd6ab62e)

[Rudometov]

/integrate

[openjdk]

@Rudometov
Your change (at version fd6ab62) is now ready to be sponsored by a Committer.

[shipilev]

/sponsor

[openjdk]

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

• 023f651: 8279536: jdk/nio/zipfs/ZipFSOutputStreamTest.java timed out
• 8f4a3a5: 8273880: Zero: Print warnings when unsupported intrinsics are enabled
• 3f79952: 8278826: Print error if Shenandoah flags are empty (instead of crashing)
• 112ea1d: 8277866: gc/epsilon/TestMemoryMXBeans.java failed with wrong initial heap size
• a167975: 8280391: NMT: Correct NMT tag on CollectedHeap
• 7a111ea: 8290374: Shenandoah: Remove inaccurate comment on SBS::load_reference_barrier()
• 728dc4d: 8296083: javax/swing/JTree/6263446/bug6263446.java fails intermittently on a VM
• 1c13d7e: 8290839: jdk/jfr/event/compiler/TestJitRestart.java failed with "RuntimeException: No JIT restart event found: expected true, was false"

Your commit was automatically rebased without conflicts.

[openjdk]

@shipilev @Rudometov Pushed as commit 94b9081.

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