151933 2015-12-07 00:49:20 -0800 Tapping on <body> doesn't fire click events 2022-02-08 23:21:39 -0800 1 1 1 Unclassified WebKit DOM Safari 9 iPhone / iPad iOS 10 RESOLVED FIXED http://patrickhlauke.github.io/touch/tests/event-listener-body-clickable.html HasReduction, InRadar, W3CTest P2 Normal --- 159753 1 webkit webkit-unassigned benjamin bfulgham redux simon.fraser webkit-bug-importer oldest_to_newest 1146776 0 webkit 2015-12-07 00:49:20 -0800 Testcases: 1. http://patrickhlauke.github.io/touch/tests/event-listener-body.html 2. http://patrickhlauke.github.io/touch/tests/event-listener-body-clickable.html The 2nd testcase uses an `onclick="void(0)"` attribute (per https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/HandlingEvents/HandlingEvents.html#//apple_ref/doc/uid/TP40006511-SW6 ) and a `cursor:pointer` CSS style (per Internet lore) to try to make the element (in our case, <body>) clickable in iOS Safari. Steps to reproduce: 1. Open one of the testcases in Safari in iOS 9.1. 2. Tap the indicated blue area of the webpage. Expected results: In the gray event log box (located below the text "Events (other than mousemove) targeted at the <body> element:"), there should be a line that says "click", indicating that a `click` event was fired at the <body> element as a result of the tap. (There will be other lines for other events that were also fired, e.g. `touchstart`) Actual results: No `click` event is recorded in the gray log box, indicating that no `click` event was fired at the <body> element as a result of the tap. --- Additional info: Per the specs, <body> isn't special-cased with regard to the `click` event, and should fire clicks just like any other element. Android Chrome follows the expected behavior. I strongly suspect IE/Edge Mobile also follows the expected behavior, but that's awaiting confirmation from a friend with a relevant device. If changing the default behavior isn't feasible, then at a minimum I'd hope for there to be some way (similar to the `onclick="void(0)" / `cursor:pointer` tricks) of requesting that <body> fire click events. 1156147 1 webkit-bug-importer 2016-01-16 01:29:14 -0800 <rdar://problem/24219436> 1156381 2 webkit 2016-01-18 04:49:59 -0800 Relevant W3C web-platform-test: http://w3c-test.org/uievents/order-of-events/mouse-events/click-on-body-manual.html 1385892 3 simon.fraser 2018-01-04 12:44:53 -0800 *** Bug 171105 has been marked as a duplicate of this bug. *** 1385893 4 simon.fraser 2018-01-04 12:45:25 -0800 <rdar://problem/5844416> 1503319 5 lforschler 2019-02-06 09:19:08 -0800 Mass move bugs into the DOM component. 1839030 6 bfulgham 2022-02-08 23:21:39 -0800 Part of this was fixed here: Committed r237658: <https://trac.webkit.org/changeset/237658> And part here: Committed r237978: <https://trac.webkit.org/changeset/237978>