Best practice: what is the best way to subscribe to events?

Question

JavaScript

I use OOP and jquery to subscribe to events, in VK files I noticed that the subscription to events occurs in html using onclick, onmousedown, etc. So there was a vprobros, how best to subscribe? What are the + and - of these methods?

Answer 1

Subscribing to events via HTML element attributes is bad in two ways:
1) It mixes markup and behavior. This means that in order to figure out what is happening, you need to alternately look into *.html and *.js, there are more chances to break something inadvertently or make a stupid mistake like a typo.
2) You can't hang more than one handler through an attribute.
However, with all of the above, it can be convenient if the code is extremely small. If your entire page consists of a calculator with three fields and two buttons, it makes no sense to include a framework there and fanatically follow all the best practices.

I noticed in VK files

The developers of VK, despite the incredible promotion of the service, are ordinary assholes, at least in terms of the front-end.

Answer 2

$('.element').on('eventName', function () {...}); // обычная подписка
$(document).on('eventName', '.element', function () {...}); // делегирование событий

Answer 3

The only thing I try to sign via HTML is the magic return false, and only because of the difficulty with IE ( event.returnValue/preventDefaullt, as well as e||event).
I don’t see the point in hanging something else, it’s very inconvenient. Starting from that. that no context is passed to the function, ending with a limit of only 1 handler. In addition, you will either have to score window, creating many functions in the global scope, or shove all the handlers into one object as methods and complicate your life. But still, the main inconvenience is that in which case you have to run to HTML to see what a certain function does, and if its different parts are also divided into files...