The 2nd testcase uses an `onclick="void(0)"` attribute (per
) 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.
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`)
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.
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.
Relevant W3C web-platform-test:
*** Bug 171105 has been marked as a duplicate of this bug. ***
Mass move bugs into the DOM component.