Based on the ui events spec the click must be sent to the nearest common ancestor of down and up events and it doesn't talk about the interactive elements at all.
related bugs: issue 163854 and issue 310263
However, back then it caused some regressions (e.g. issue 328304 and issue 329136 ) so we never went beyond an interactive element boundary to find the common parent to match IE11 behavior. Nowadays, it seems both Edge and WebKit are firing click events to the nearest common parent irrespective of interactive elements. So it might be the time for Chrome to also change and follow the spec.
FF is also looking to follow the same behavior here.
Comment 1 by bugdroid1@chromium.org
, Aug 3