The target of these events will always be an Element of some sort, according to https://w3c.github.io/uievents/#topmost-event-target. I've also confirmed this with https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=10374 in Chrome, Firefox and Safari – I can't get the event to fire at Document or Window.

So I think we should have these entries either on Element or on HTMLElement + SVGElement + MathMLElement, and think that it should probably be Element. I'll try to test if the event can be fired on an element not in a known namespace.

I've confirmed with https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=10375 in Chrome, Firefox and Safari that a plain Element instance can be the target of "click" elements, so I think we should put these events on Element only.

Also, can you link to both https://w3c.github.io/uievents/#click and https://html.spec.whatwg.org/multipage/webappapis.html#handler-onclick in the resulting entries here?

This pull request has merge conflicts that must be resolved before it can be merged.

This pull request has merge conflicts that must be resolved before it can be merged.

@queengooborg can you review the Element vs. HTMLElement + SVGElement question?

This pull request has merge conflicts that must be resolved before it can be merged.

This pull request has merge conflicts that must be resolved before it can be merged.

This pull request has merge conflicts that must be resolved before it can be merged.

This pull request has merge conflicts that must be resolved before it can be merged.

This pull request has merge conflicts that must be resolved before it can be merged.

This pull request has merge conflicts that must be resolved before it can be merged.