You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for an issue that matches the one I want to file, without success.
Issue Details
Electron Version: 8 (but same in sources)
Operating System: Windows 10 (1909)
Last Known Working Electron version: N/A
Expected Behavior
In the Debugger.message event, it is necessary to get the sessionId to be able to distinguish messages relevant to the page versus any iframes, service workers, etc. I would expect the session ID to be given in the event callback.
Actual Behavior
The debugger domain does not expose these.
Messages are emitted only with the method and params, but not the session ID
The fiddle connect the debugger to a page with an iframe, and attaches to all targets. It logs all the arguments/data sent in the message event. Observe that the session ID is missing; there's no way to distinguish which frame the scriptParsed events are coming from.
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Issue Details
Expected Behavior
In the Debugger.message event, it is necessary to get the
sessionId
to be able to distinguish messages relevant to the page versus any iframes, service workers, etc. I would expect the session ID to be given in the event callback.Actual Behavior
The debugger domain does not expose these.
Messages are emitted only with the method and params, but not the session ID
electron/shell/browser/api/electron_api_debugger.cc
Line 67 in e1e73fa
In CDP these messages would normally come like:
To Reproduce
Fiddle: https://gist.github.com/c480df80e612d06befb2d7068f0aff6e
The fiddle connect the debugger to a page with an iframe, and attaches to all targets. It logs all the arguments/data sent in the
message
event. Observe that the session ID is missing; there's no way to distinguish which frame the scriptParsed events are coming from.The text was updated successfully, but these errors were encountered: