<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Tapping on <body> doesn't fire click events"
href="https://bugs.webkit.org/show_bug.cgi?id=151933">151933</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Tapping on <body> doesn't fire click events
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>Safari 9
</td>
</tr>
<tr>
<th>Hardware</th>
<td>iOS
</td>
</tr>
<tr>
<th>OS</th>
<td>iOS 9.0
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>HTML Events
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>webkit@chrisrebert.com
</td>
</tr></table>
<p>
<div>
<pre>Testcases:
1. <a href="http://patrickhlauke.github.io/touch/tests/event-listener-body.html">http://patrickhlauke.github.io/touch/tests/event-listener-body.html</a>
2. <a href="http://patrickhlauke.github.io/touch/tests/event-listener-body-clickable.html">http://patrickhlauke.github.io/touch/tests/event-listener-body-clickable.html</a>
The 2nd testcase uses an `onclick="void(0)"` attribute (per
<a href="https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/HandlingEvents/HandlingEvents.html#//apple_ref/doc/uid/TP40006511-SW6">https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/HandlingEvents/HandlingEvents.html#//apple_ref/doc/uid/TP40006511-SW6</a>
) 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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>