Test case: https://jsfiddle.net/dpogue/p1bduqyo/2/
Clicking an element with `pointer-events: none` CSS should fire a click event targeting its parent. In this case, Safari fires the event on a parent higher up in the DOM rather than the immediate parent element.
Chrome and Firefox fire the click event with the correct parent
IE and Edge incorrectly fire the click event on the element (which is contrary to `pointer-events: none` behaviour)
Mass move bugs into the DOM component.
Pointer events are UI events.
Pointer Events != CSS pointer-events property. But yeah, this is probably the right component.