Because we actually replay the browser session as it ran before, Replay collects all of the event handlers that ran while recording. This means that all the mouse events, worker messages, or even uncaught promises are available for inspecting and debugging.

[View replay](https://www.loom.com/share/9f16bce647354353814ddd659af0b22f)

View replay

Viewing events

Events are shown in the Events pane in the left sidebar and can be output to the Console.

The Events pane is within the Replay Info panel. Click on an event to jump to that time in the replay. The video and console will update to reflect the application at that point in time.

<aside> 💡 Sometimes one event is handled multiple times. This can be surprising at first, but it's pretty common for one mouse click to have a lot of handlers.

</aside>

Jump to code

Time travel from click and keystroke events into their React onClick and onKeyPress handlers. Jump to code takes you to the relevant code where you can begin debugging with print statements.

<aside> ⚛️ Often libraries like React will install their own global handler and then pass the event to a component event handler like onClick. We do our best to map these, but if you see an issue please let us know by submitting a bug report.

</aside>