Bug: Clicks on blocked(?)/svg elements do not contain node information

[billyvg]

Here's an example replay: https://sentry.sentry.io/replays/javascript:7e4dbf7600bf4768a14ef2ede665fe92/?project=11276&query=&referrer=%2Freplays%2F&statsPeriod=14d&t_main=dom&yAxis=count%28%29 and here is the crumb data it produces:

I think if the node is not serialized, we should lookup its parent.

Another aspect of this ticket is that we sometimes are capturing the leaf node which is not necessarily the most user friendly in regards to search for clicks. This could be the difference between target and currentTarget in the click event? This happens with svgs/images.

[mydea]

Hmm, I wonder how we can/should fix this. We could try to walk up from an element to find the closest interactive parent, but IMHO that is probably hard to do, as there may not be one (it is not good practice, but totally valid to do so).

We could try to look up the parents with a custom selector, e.g.

const interactiveParents = 'a[href], button, [tabindex]:not([tabindex="-1"])';
if(targetNode.__sn.closest(interactiveParents) {
  // use this instead
}

but I guess this could also have unexpected side effects 🤔