Safari itself is not open source so it's unclear how much/little they have modified WebKit and the JavaScript engine. Given that this bug involves JS (events not firing), and MacOS doing its own thing with JS, it's entirely possible that this is a Safari only bug that resides in the proprietary parts of the codebase...
'Cause if it isn't then it's not really a good proxy for testing Safari behavior in this context...