Bug 61212
| Summary: | Add a test that shows WKView isn't calling ::SetCursor too often | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Adam Roben (:aroben) <aroben> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | Keywords: | PlatformOnly |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
Adam Roben (:aroben)
We need a test that shows that bug 61211. Specifically, we should test that WKView is only calling ::SetCursor in response to WM_SETCURSOR.
We might be able to write a test that subclasses the WKView, overrides WM_SETCURSOR to set a custom cursor, moves the mouse, and then later checks that that ::GetCursor returns the custom cursor instead of whatever WKView would have set the cursor to.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
*** This bug has been marked as a duplicate of bug 61213 ***