Bug 98016

Summary: Fake mousemove event fired with current mouse position still uninitialized
Product: WebKit Reporter: Alexander Pavlov (apavlov) <apavlov>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal    
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Test case none

Alexander Pavlov (apavlov)
Reported 2012-10-01 04:33:30 PDT
Created attachment 166450 [details] Test case Open the attachec test case (quoted below). Reload it using a keyboard shortcut and do NOT move your mouse afterwards. Observe the foo's color being red, as if it were hovered. Any mousemove over the page updates the container to give it the right color. ----8<---- <style> #container { position: absolute; top: 0; left: 0; width: 100px; height: 100px; border: 1px solid black } #container:hover { color: red; } </style> <body> <div id="container"> <div id="foo">Should NOT be red immediately upon load</div> </div> <style> #foo { cursor: hand; } </style> </body> ----8<----
Attachments
Test case (319 bytes, text/html)
2012-10-01 04:33 PDT, Alexander Pavlov (apavlov)
no flags
Alexander Pavlov (apavlov)
Comment 1 2012-12-29 00:01:16 PST
*** This bug has been marked as a duplicate of bug 104861 ***
Lucas Forschler
Comment 2 2019-02-06 09:19:00 PST
Mass move bugs into the DOM component.
Note You need to log in before you can comment on or make changes to this bug.