[NTUSER] Use MOUSEEVENTF_XDOWN/XUP in the X-button flush checks (#9122)

This fixes the mismatch, where the flush checks wrongly tested `mi.dwFlags` (`MOUSEEVENTF_XDOWN/XUP`) against the raw `MOUSE_BUTTON_4/5` bits, so the combined button-4+5 events were flushed in the wrong block or were dropped.
This commit is contained in:
Ahmed Arif
2026-06-08 23:59:52 +02:00
committed by GitHub
parent 3511472586
commit 2dddf48071
+2 -2
View File
@@ -92,7 +92,7 @@ UserProcessMouseInput(PMOUSE_INPUT_DATA mid)
}
/* If mouseData is used by button 4, send input and clear mi */
if (mi.dwFlags & (MOUSE_BUTTON_4_DOWN | MOUSE_BUTTON_4_UP))
if (mi.dwFlags & (MOUSEEVENTF_XDOWN | MOUSEEVENTF_XUP))
{
UserSendMouseInput(&mi, FALSE);
RtlZeroMemory(&mi, sizeof(mi));
@@ -111,7 +111,7 @@ UserProcessMouseInput(PMOUSE_INPUT_DATA mid)
}
/* If mouseData is used by button 5, send input and clear mi */
if (mi.dwFlags & (MOUSE_BUTTON_5_DOWN | MOUSE_BUTTON_5_UP))
if (mi.dwFlags & (MOUSEEVENTF_XDOWN | MOUSEEVENTF_XUP))
{
UserSendMouseInput(&mi, FALSE);
RtlZeroMemory(&mi, sizeof(mi));