Issue 4067: AutomationProvider::WindowSimulateDrag is full of fail
http://code.google.com/p/chromium/issues/detail?id=4067
New issue report by [EMAIL PROTECTED]:
1. AutomationProvider::WindowSimulateDrag sends WM_LBUTTONDOWN etc _client_
messages to a window regardless of whether or not the points specified in
|drag_path| are over client areas of the window.
2. The function calls SetCursorPos assuming the points in |drag_path| are
in screen coordinates, but actually they're in client coordinates.
These two issues turn out to be a major source of tab UI test flakiness.
Issue attributes:
Status: Assigned
Owner: [EMAIL PROTECTED]
Labels: Type-Bug Pri-1 OS-All Area-BrowserUI Mstone-1.0
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
