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

Issue 725462 link

Starred by 1 user
Status: Duplicate
Merged: issue 716694
Owner:
tkent@chromium.org
Closed: May 2017
Cc:
█ hdodda@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

parentNode.appendChild(elem) in mousedown event handler prevents click event handler from getting called

Reported by vignesh1...@gmail.com, May 23 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. attach a mousedown event handler that executes: "this.parentNode.appendChild(this);"
2. attach a click event handler 
3. click on the element
4. the click event handler will not be called

What is the expected behavior?
after the mousedown handler is called, click handler should be called

What went wrong?
It breaks click event handler

Did this work before? Yes 57

Does this work in other browsers? Yes

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 25.0 r0

Here is a demo: http://plnkr.co/edit/LGJuNIxOtHFaDLjROMGH?p=preview
chromebug.zip
1.1 KB Download

Comment 1 by vignesh1...@gmail.com, May 23 2017 

This issue breaks double click event handler in this D3 visualization as well: http://bl.ocks.org/Neilos/584b9a5d44d5fe00f779

Comment 2 by ligim...@chromium.org, May 23 2017

Labels: Needs-Triage-M58 Needs-Bisect

Comment 3 by hdodda@chromium.org, May 24 2017

Cc: hdodda@chromium.org
Labels: -Pri-2 -Needs-Bisect hasbisect-per-revision M-60 OS-Linux OS-Mac Pri-1
Owner: tkent@chromium.org
Status: Assigned (was: Unconfirmed)
Tested the issue on windows 7 , ubuntu 14.04 and Mac OS 10.12.4 using chrome M58 #58.0.3029.110 and M60 #60.0.3108.0 and issue is reproduced.

This is a regression issue broken in M58.

Using the per-revision bisect providing the bisect results,
Good build: 58.0.3006.0 (Revision: 448862).
Bad build: 58.0.3008.0 (Revision: 449509).

You are probably looking for a change made after 448927 (known good), but no later than 448928 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspectas some perf builds might get missing due to failure.

 https://chromium.googlesource.com/chromium/src/+log/a79a95466df9d013721167cf2f0c8ba849214207..1c12127b721f833f37b81553e19b8eb0392da651

From the CL above, assigning the issue to the concern owner 

@tkent - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Review-Url: https://codereview.chromium.org/2496133002

Thanks!

Comment 4 by tkent@chromium.org, May 24 2017

Components: -Blink>DOM Blink>Input
Mergedinto: 716694
Status: Duplicate (was: Assigned)
►

Sign in to add a comment