I presume there must be some existing "Why isn't my <div> clickable?" bug of which this will be a duplicate,
but my search-fu wasn't able to turn up anything and there's now an actual web-platform-test for this, so...
that elements only fire `click` events in certain circumstances (e.g. is a <button>, has an `onclick`, is styled as `cursor: pointer;`, etc.).
However, the W3C spec that defines the `click` event doesn't place any such special preconditions on which elements fire `click` events.
Quoting from relevant portions of the spec:
> The click event type must be dispatched on the topmost event target indicated by the pointer,
> when the user presses down and releases the primary pointer button,
> or otherwise activates the pointer in a manner that simulates such an action.
> topmost event target
> The *topmost event target* must be the element highest in the rendering order which is capable of being an event target.
> In graphical user interfaces this is the element under the user's pointing device. [...]
Set the URL field to the relevant web-platform-test.
Mass move bugs into the DOM component.