[JEWEL-1188] Caret not moving when the popup is visible

[wellingtoncosta]

Summary

Fixes an issue where clicking in an editable combo box text field while a popup is visible would dismiss the popup but fail to move the caret to the clicked position. Only happens with Custom Popup Renderer enabled.

The AWTEventListener was consuming all mouse press events that triggered popup dismissal, including clicks on the owner component (editable combo box). When the event was consumed, it never reached the text field component, preventing caret repositioning.

Solution

Removed the event.consume() in the MouseEvent branch and leave the consume to happen in the compose layer, as it's done for the WindowEvent logic.

Release notes

Bug fixes

• Fixed caret not moving when clicking in an editable combo box text field while its popup is visible

---

Note

Fixes lost click handling when dismissing JDialog popups, ensuring clicks propagate to owner components for caret movement.

• In JDialogRenderer.kt, remove event.consume() from the AWTEventListener MouseEvent path that triggers onDismissRequest
• Keeps dismissal behavior intact for WindowEvent; compose layer now handles consumption

^{Written by Cursor Bugbot for commit f7875bd. This will update automatically on new commits. Configure here.}

[faogustavo]

Something I noticed while I was testing the PR is that only skipping the event consumption is enough to fix the problems. The EditableComboBox has the logic to skip the onDismissRequest() call.

Maybe we can just remove the event.consume() and leave the consume to happen in the compose layer so it can handle cursor position changes/etc

[wellingtoncosta]

Something I noticed while I was testing the PR is that only skipping the event consumption is enough to fix the problems. The EditableComboBox has the logic to skip the onDismissRequest() call.

Maybe we can just remove the event.consume() and leave the consume to happen in the compose layer so it can handle cursor position changes/etc

You mean to just keep the currentOnDismissRequest?.invoke()? Haven't tested that, but I can check it out.