[Bug 51476] New: user32:input test_Input_mouse() gets bad WM_MOUSEMOVE messages

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51476

Bug ID: 51476
           Summary: user32:input test_Input_mouse() gets bad WM_MOUSEMOVE
                    messages
           Product: Wine
           Version: 6.10
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: [e-mail]
          Reporter: [e-mail]

user32:input gets the following failure on most Windows versions:

http://winetest.dolphin/data/patterns.html#user32:input

input.c:3350: Test failed: got unexpected WM_MOUSEMOVE x 150, expected 210

* The invalid x value depends on the machine (e.g. it's different on
win81_cw-rx460 and w8), but is the same from one run to the next.
* The failure is quite frequent but not 100% reproducible (e.g. on w8). Timing
issue?
* It impacts Windows 7 to Windows 10 2009 (except w1064v1607).

[Bug 51476] user32:input test_Input_mouse() gets bad WM_MOUSEMOVE messages

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51476

François Gouget  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |source, testcase

[Bug 51476] user32:input test_Input_mouse() gets bad WM_MOUSEMOVE messages

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51476

--- Comment #1 from François Gouget  ---
The effective pt.x value is not always the same: it varies between 150 and 284.
But the expected value is always 210.