Nice to say, but the other side in this case would likely be the inside of a third-party library. If it was in-repo code, it could have just been fixed to not r

Nice to say, but the other side in this case would likely be the inside of a third-party library. If it was in-repo code, it could have just been fixed to not require a stopPropagation workaround!