UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Go to a website with HEAVY DOM manipulation and click handlers on consecutive children elements to a common ancestor(have had the issue several times on AWS, Pluralsight, and forms that use click handlers to manage State including React based pages)
2. Begin DOM manipulation(changing number and content) that will lower the amount of DOM nodes with click handlers, and then increase it
3. Use a click handler on the second to last element or compare the two click handlers

What is the expected behavior?
The click handler to the proper child fires

What went wrong?
The click handler on the last element fires, not the click handler on the second to last element

It is always the second to last element having the final elements' click handler

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 66.0.3359.181  Channel: stable
OS Version: 10.0
Flash Version: 

Repeating this has been reliable, but the amount of changes to trigger the issue is unreliable. I have noticed on as little as a single pass of changing the amount of DOM nodes, however it is rare that it happens that quickly. Sometimes it can take tens of child length changes before it happens, and immediately after it is fine on the next change of length

It is most repeatable when there is a heavy amount of DOM manipulation within a single redraw