Created attachment 315605 [details] Testcase See the attached test case. It has a <div> with a child <div>, both the parent and the child have the same initial, overlapping bounds. The parent shows an alert when receiving a "click" event, the child shrinks itself to 25% of its size using a "transform: scale(25%)" style when the ":active" pseudo-class matches. If you click in the center of the parent, the "click" event is dispatched. If you click on the left, top, right or bottom of the parent, there is no "click" event dispatched, seemingly because the original event target, the child, is no longer hit-testing by the time the mouse pointer is released. Firefox behaves the same as WebKit, but Chrome dispatches the "click" event in all cases, which seems correct to me.
<rdar://problem/33340234>
This causes https://bugs.webkit.org/show_bug.cgi?id=174565.
If/when this gets fixed, we should remove the workaround for https://bugs.webkit.org/show_bug.cgi?id=174565.
So the question is whether :active style is applied before or after the click? :active applies at mouseDown time, and click fires after mouseDown/mouseUp, so I think our behavior is correct.
In EventHandler::handleMouseReleaseEvent(const PlatformMouseEvent&), we end up with targetNodeForClickEvent() with a mousePressNode being the child and a mouseReleaseNode being the parent node. The logic inside targetNodeForClickEvent() returns nullptr in this case so we do not fire a click event. It sounds like we would want to fire the click event at the mouseReleaseNode instead? I'll look up the spec and check the blink code as well.
From https://w3c.github.io/uievents/: """ Each implementation will determine the appropriate hysteresis tolerance, but in general SHOULD fire click and dblclick events when the event target of the associated mousedown and mouseup events is the same element with no mouseout or mouseleave events intervening, and SHOULD fire click and dblclick events on the nearest common inclusive ancestor when the associated mousedown and mouseup event targets are different. """ So it sounds like we are supposed to fire the click event at the nearest common ancestor. In the test case, that would be the parent node.
Created attachment 315677 [details] Patch
Comment on attachment 315677 [details] Patch Clearing flags on attachment: 315677 Committed r219568: <http://trac.webkit.org/changeset/219568>
All reviewed patches have been landed. Closing bug.