Verified on Linux in both 54.0.2840.100 stable and 56.0.2924.3 unstable.

I have an extension that uses the debugger API.

When I type inside a text <INPUT> field and then click outside of that field, then usually the page sees a 'change' on the input field followed by the 'click' event.

But when the extension invokes DOMDebugger.setEventListenerBreakpoint for 2 eventNames, 'change' and 'click', then the page only sees the 'change' event.

The extension is calling Debugger.resume after the break on the 'change' event. I see the page getting the 'change' event as usual, but the 'click' is gone. I also observe that the debugger "resumed" event comes a bit later.

Sequence of logs:

- break on 'change'
- invoke Debugger.resume()
- page sees 'change'
- ...
- debugger event: resumed

Sequence of logs if the extension only breaks on 'click':

- break on 'click'
- invoke Debugger.resume()
- page sees 'change'
- page sees 'click'

Expected sequence of events with breaking on both 'click' and 'change':

- break on 'change'
- invoke Debugger.resume()
- page sees 'change'
- break on 'click'
- invoke Debugger.resume()
- page sees 'click'