Bug 151933

Summary:	Tapping on <body> doesn't fire click events
Product:	WebKit	Reporter:	Chris Rebert <webkit>
Component:	DOM	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED FIXED
Severity:	Normal	CC:	benjamin, bfulgham, redux, simon.fraser, webkit-bug-importer
Priority:	P2	Keywords:	HasReduction, InRadar, W3CTest
Version:	Safari 9
Hardware:	iPhone / iPad
OS:	iOS 10
URL:	http://patrickhlauke.github.io/touch/tests/event-listener-body-clickable.html
Bug Depends on:
Bug Blocks:	159753

Chris Rebert

Reported 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.