Very useful to track down where some, sometimes pesky, JavaScript code has bound events to the DOM.
This is a big debugging pain, to track down why events are being triggered, or not working, in a certain way and what JavaScript code is responsible for it.
> What do mean by monitoring? Would be interested in hearing more about what you're talking about and the use cases.
Maybe I expressed myself incorrectly. I mean this type of information profiling.
https://developers.google.com/chrome-developer-tools/docs/ti...
Very useful to track down where some, sometimes pesky, JavaScript code has bound events to the DOM.
This is a big debugging pain, to track down why events are being triggered, or not working, in a certain way and what JavaScript code is responsible for it.