[Webkit-unassigned] [Bug 151933] New: Tapping on <body> doesn't fire click events

Mon Dec 7 00:49:20 PST 2015

https://bugs.webkit.org/show_bug.cgi?id=151933

            Bug ID: 151933
           Summary: Tapping on <body> doesn't fire click events
    Classification: Unclassified
           Product: WebKit
           Version: Safari 9
          Hardware: iOS
                OS: iOS 9.0
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: HTML Events
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: webkit at chrisrebert.com

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20151207/fe2f9b21/attachment.html>