Chrome Developer Tools - monitorEvents

I have been playing with the Chrome Developer Tools lately. Here is a cool feature I didn’t know about.

There are many times I have run some code in the console simply to bind to an event and simply log the result.

$("body").bind("click mousedown", function(e) {

There is a built in alternative called monitorEvents. Here is a quick demo on how to use it:

Inspect an element (see screenshot). Now that it has been inspected, there is a $0 variable available in the console.

Instead of that extra bind, you can just type this into the console:

monitorEvents($0, 'mouse')

Which, if you have the body selected in the Elements panel, is equivalent to typing:

monitorEvents(document.body, 'mouse')

OK, now that you can see all these events in the console and you have tracked down your issue, you probably want them to stop! Luckily, there is an unmonitorEvents function to do this.


You can also use ‘key’ instead of ‘mouse’ if you are tracking key events. There are actually a number of second parameters, but the support between Firebug and Devtools varies.

Possible Arguments For Firebug’s monitorEvents

Via the Firebug command line API

composition contextmenu drag focus form key load mouse mutation paint scroll text ui xul

Possible Arguments For DevTools monitorEvents

Thanks to Paul Irish dropping by in the comments and linking to the source, we now know all the officially supported DevTools keywords:

mouse key touch control

Map of Events for DevTools monitorEvents:

mouse:  "mousedown", "mouseup", "click", "dblclick", "mousemove", "mouseover", "mouseout", "mousewheel"
key: "keydown", "keyup", "keypress", "textInput"
touch:  "touchstart", "touchmove", "touchend", "touchcancel"
control:  "resize", "scroll", "zoom", "focus", "blur", "select", "change", "submit", "reset"
no arguments: all of the above + "load", "unload", "abort", "error", "select", "change", "submit", "reset", "focus", "blur", "resize", "scroll", "search", "devicemotion", "deviceorientation"


  1. Paul Irish Says:

    Here’s the source of monitorEvents:$&type=cs&l=698

    Which translates to…

    * If the second argument is ‘mouse’, you’ll get all “mousedown”, “mouseup”, “click”, “dblclick”, “mousemove”, “mouseover”, “mouseout”, “mousewheel” events
    * If the second argument is ‘key’, you’ll get all “keydown”, “keyup”, “keypress”, “textInput” events
    * If the second argument is ‘touch’, you’ll get all “touchstart”, “touchmove”, “touchend”, “touchcancel” events. (See emulate touch events in devtools settings!!)
    * If the second argument is ‘control’, you’ll get all “resize”, “scroll”, “zoom”, “focus”, “blur”, “select”, “change”, “submit”, “reset” events.
    * If you don’t define a second argument, you’ll get all of the above, plus… “load”, “unload”, “abort”, “error”, “select”, “change”, “submit”, “reset”, “focus”, “blur”, “resize”, “scroll”, “search”, “devicemotion”, “deviceorientation” .


  2. Brian Says:

    Thanks Paul!
    Always more accurate to see the actual source to figure out support than just wild speculation :). I actually think I had tried to find this before but had limited my search to the front-end/ directory.

    Up until now I have been using this link to view inspector source: But it always bothered me that I couldn’t search (for instances this these) – that code search is awesome. I will bookmark

  3. Johnny Says:

    Awesome, thank you.

  4. Tony Says:

    Good find.

    FYI: You can say “I ran” or “I have run” but you can’t say “I have ran” without sounding weird.

  5. Aaron Frost Says:

    Brian, this is a great share! Thank you for doing the ground work here and sharing it out.

    I didn’t know about either the $0 var that is created when you inspect an obj OR the monitorEvents/unmonitorEvents methods. Now I can detach a little from console.log.

  6. Brian Says:

    Thanks! If you want more tips like these, check out some of the videos Paul Irish has made (where I learned about many of the devtools features). Watch this one first: – it is definitely worth the 5 minutes. And I’ll keep posting tips here as I find them!

  7. Magento addon Says:

    Magento addon…

    […]Chrome Developer Tools – monitorEvents – Brian Grinstead[…]…

  8. Вся правда о Chrome (и не только) Web Inspector. Часть 1 Says:

    […] monitorEvents (англ.) — Немного о monitorEvents […]

  9. 23 Marzo 2013 alle 09:27 Says:

    23 Marzo 2013 alle 09:27…

    Chrome Developer Tools – monitorEvents – Brian Grinstead…

  10. 使用chrome调试工具来监听事件 « serendipity的技术小宅 Says:

    […] […]

  11. Leander Says:

    I can’t get monitorEvents to work. It says monitorEvents isn’t defined.

  12. Brian Says:

    You can only call monitorEvents from within the console. If you try to call it from your program you will get the “monitorEvents is not defined” error.

  13. edson Says:

    thanks a lot bro

  14. Chrome Developer Tools – monitorEvents | Says:

    […] Source […]

  15. Angelo Says:

    Nice article, I have written a guide to help you all.
    Let me know if you find it useful:


  16. touch event is firing on wrong element Says:

    […] device. then launch debug tools. type monitorEvents(document.body,"touch") on the console, see this. now tap on the circle: sometimes the event target is img but at other times it is the canvas. […]

  17. Does Google Chrome MonitorEvent support custom events? Says:

    […] per How do I view events fired on an element in Chrome Web Developer? and, I can use MonitorEvent to monitor events in chrome. However, I am not sure if this supports custom […]

  18. Chris Says:

    Does EventMonitor also support custom events?
    For example, I have a custom event bound by jQuery using $(document).bind(‘connect’, function (ev, data) {//code here;});

    but if I type monitorEvents($0, ‘connect’) into the console

    I don’t see any monitored events, even though the event is most definitely triggered in my code.



  19. Brian Says:

    Here is the current source code for it: In _normalizeEventTypes it looks like if it is not a recognized string (like ‘connect’), it will be added to the list of types to listen to anyway. So if the event could be detected with addEventListener I expect that it should also log.

  20. Brian Says:

    Try adding something like this at the same time you do the monitorEvents and see if it logs: `$0.addEventListener(“connect”, function() {console.log(“connect”); });`

  21. Rakesh Juyal Says:

    Looks like it doesn’t work anymore.
    monitorEvents($0, 'mouse')

    doesn’t work any more.

  22. Sergiu Says:

    You can simply put monitorEvents(window, someEvent); Some event can be any function attached to a global object. (window events, jquery functions, any library you load etc)

  23. Gajendra Singh Says:

    For those you directly need to know which event is on an element and where its location is in the code, Can use chrome extension

  24. Sigma Says:

    mouseenter , mouseleave are also supported . (41.0.2272.118 m)

  25. View Javascript Events Fired on Element in Google Chrome | Says:

    […] can use monitorEvents […]

  26. Single Wheel Hover Wheel Says:

    thanks for sharing

  27. erknrio Says:

    Awesome extensión Gajendra Singh, thanks for sharing.

  28. monitorEvents | Chrome Dev Tools Says:

    […] Chrome Developer Tools – monitorEvents […]

  29. thefonso Says:

    UPDATE: Paul’s original posted link is now 404.

    I think the webkit source is now located at this location ..

    And monitorEvents is located at this new location ….

Comments are closed. Please contact me instead.