Bug 151933 - Tapping on <body> doesn't fire click events
Summary: Tapping on <body> doesn't fire click events
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: HTML Events (show other bugs)
Version: Safari 9
Hardware: iPhone / iPad iOS 10
: P2 Normal
Assignee: Nobody
URL: http://patrickhlauke.github.io/touch/...
Keywords: HasReduction, InRadar, W3CTest
: 171105 (view as bug list)
Depends on:
Blocks: 159753
  Show dependency treegraph
 
Reported: 2015-12-07 00:49 PST by Chris Rebert
Modified: 2018-01-04 12:45 PST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Rebert 2015-12-07 00:49:20 PST
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.
Comment 1 Radar WebKit Bug Importer 2016-01-16 01:29:14 PST
<rdar://problem/24219436>
Comment 2 Chris Rebert 2016-01-18 04:49:59 PST
Relevant W3C web-platform-test:
http://w3c-test.org/uievents/order-of-events/mouse-events/click-on-body-manual.html
Comment 3 Simon Fraser (smfr) 2018-01-04 12:44:53 PST
*** Bug 171105 has been marked as a duplicate of this bug. ***
Comment 4 Simon Fraser (smfr) 2018-01-04 12:45:25 PST
<rdar://problem/5844416>