Skip to content

Post WM_SETCURSOR after WM_ACTIVATE to workaround XAML island busy cursor#20448

Open
Zeroes1 wants to merge 1 commit into
microsoft:mainfrom
Zeroes1:Cursor-busy-xaml-island-wm-setcursor
Open

Post WM_SETCURSOR after WM_ACTIVATE to workaround XAML island busy cursor#20448
Zeroes1 wants to merge 1 commit into
microsoft:mainfrom
Zeroes1:Cursor-busy-xaml-island-wm-setcursor

Conversation

@Zeroes1

@Zeroes1 Zeroes1 commented Jul 19, 2026

Copy link
Copy Markdown

After activation, Windows Terminal may show a BUSY (IDC_APPSTARTING)
cursor because the XAML island is busy processing the activation and
does not respond to WM_SETCURSOR in time. Post a WM_SETCURSOR message
to force re-evaluation once XAML is idle.

This is a workaround for a limitation in WinUI XAML islands which can
block synchronous window messages while busy.

Close: #18662

Checked only under win10. It's works.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Comment thread src/cascadia/WindowsTerminal/IslandWindow.cpp Fixed
@github-actions

This comment has been minimized.

@Zeroes1
Zeroes1 force-pushed the Cursor-busy-xaml-island-wm-setcursor branch from 900e82a to 6ed286d Compare July 19, 2026 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Plagued by the throbber?

2 participants