[w3c/uievents] Click targeting is inconsistent across different UAs and the spec (#233)

@smaug---- @rniwa
Based on the current wording of the spec it seems that UA should send the click event to the first inclusive common ancestor of the down and up targets unconditionally. I added the following two wpt tests to cover this behavior:

[http://w3c-test.org/uievents/click/click_event_target_child_parent.html
](http://w3c-test.org/uievents/click/click_event_target_child_parent.html
)[http://w3c-test.org/uievents/click/click_event_target_siblings.html](http://w3c-test.org/uievents/click/click_event_target_siblings.html)

It seems that different browsers are showing different behaviors on this on different scenarios and they don't seem to agree on all the tests.
Chromium recently changed its behavior to match the spec exactly but we got some regressions. I have been working with library maintainers to fix the issues as much as I could but still wanted to bring this inconsistency issue up.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/233