[PR #18233] Fix order and robustness of CTRL_*_EVENTs #31480

Open
opened 2026-01-31 09:47:31 +00:00 by claunia · 0 comments
Owner

Original Pull Request: https://github.com/microsoft/terminal/pull/18233

State: closed
Merged: Yes


  • This fixes a regression in 391abafc, which caused attached clients
    to receive CTRL_CLOSE_EVENTs, etc., in oldest-to-newest order,
    while historically the opposite is expected.
  • It also changes the behavior of ProcessCtrlEvents to dispatch
    these events no matter whether a client is already dead.
    This restores the Windows XP to Windows 8.1 behavior.

Both of these fixes would address the issue on their own.

Closes #15373

Validation Steps Performed

  • CloseTest from our repository shows newest-to-oldest order again.
  • node gets killed when run under npm and closing the tab.
**Original Pull Request:** https://github.com/microsoft/terminal/pull/18233 **State:** closed **Merged:** Yes --- * This fixes a regression in 391abafc, which caused attached clients to receive CTRL_CLOSE_EVENTs, etc., in oldest-to-newest order, while historically the opposite is expected. * It also changes the behavior of `ProcessCtrlEvents` to dispatch these events no matter whether a client is already dead. This restores the Windows XP to Windows 8.1 behavior. Both of these fixes would address the issue on their own. Closes #15373 ## Validation Steps Performed * CloseTest from our repository shows newest-to-oldest order again. * node gets killed when run under npm and closing the tab.
claunia added the pull-request label 2026-01-31 09:47:31 +00:00
Sign in to join this conversation.
No Label pull-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#31480