New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 708799 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Calling preventDefault() on "pointerdown" event prevents subsequent "click" event from firing

Reported by jarek.fo...@gmail.com, Apr 5 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.1 Safari/603.1.30

Steps to reproduce the problem:
1. Open https://jsfiddle.net/hxq1hpna/
2. Click the red button

What is the expected behavior?
"pointerdown" and "click" events should be fired and logged into the console

What went wrong?
"click" event is not fired on Chrome 59

Did this work before? Yes 57.0.2987

Does this work in other browsers? Yes

Chrome version: 59.0.3044.0  Channel: canary
OS Version: OS X 10.12.4
Flash Version: 

pointerDownEvent.preventDefault() should not be preventing the subsequent "click" event from firing, as described by the spec: https://w3c.github.io/pointerevents/#dfn-compatibility-mapping-with-mouse-events.

This is a serious regression that might break some apps as pointerDownEvent.preventDefault() is often used to prevent widgets from receiving focus.
 
Labels: Needs-Triage-M59
Cc: msrchandra@chromium.org
Labels: Needs-Feedback
@jarek.foksa -- Thank You for the report.
Tested the URL on Latest Canary# 59.0.3064.0 and observed the following events in Console.
Clicked twice on Red box and observed the events fired as shown in the screenshot.
Please let me know if anything is missed.
Thank You.
708799.png
97.5 KB View Download

Comment 3 Deleted

@msrchandra After updating Chrome Canary to version 59.0.3064.0 I'm no longer able to reproduce this bug. It looks like it has been fixed recently.
Project Member

Comment 5 by sheriffbot@chromium.org, Apr 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: nzolghadr@chromium.org
Status: WontFix (was: Unconfirmed)
Closing as per comments #4. I wonder if this is caused by nzolghadr@ adjusted how targeting worked with captured events and the click event (which was reverted).
Yes. This was a bug in the original patch. As you said it is all reverted and it should be fine now.

Sign in to add a comment