For now, we can't know if some JS traces relates to some particular DOM events.
It would be nice to either:

• log all DOM events (independently of JS traces), most likely optionaly
• flag the top frame of each new trace with a possibly related DOM event

The first option has the flaw of logging events which may not trigger any JS code.
The latest may be subject to mismatch as we would most likely use DebuggerNotificationObserver and do a match. This match may sometime be loose or wrong.

As this is based on DebuggerNotificationObserver, this would only work
for events currently supported by this interface.
So we would typically miss network events which aren't suppported yet.