Re:Firefox has lots of room to improve if it wants to beat C...
by DCoder on Monday September 02, 2019 @01:55AM
(#20857048)
The behaviour you're referring to is actually a global property `window.event` [0]. Although it's part of the DOM spec, it's only there for historical reasons and should definitely be avoided.
[0]: https://developer.mozilla.org/en-US/docs/Web/API/Window/even...
Another bug that I believe is actually Firefox doing the right thing: if you make an event handler function but give it no parameters, Firefox will have no local named event. Chrome will create an event variable for you. Caused several "Firefox bugs" in our app.