Figure out what to do for exposing detailed ORB blocking result to developer console
Categories
(Core :: DOM: Networking, enhancement, P2)
Tracking
()
People
(Reporter: sefeng, Unassigned)
References
Details
(Whiteboard: [necko-triaged][orb:m2])
We are trying to avoid leaking information to the content process.
Someone on DOM team will handle this :)
|
||
Comment 2•2 years ago
|
||
By default, when debugging a tab, DevTools wouldn't listen for nsIScriptError/console message from the parent process, but only from the tab's content process. But we could easily start listening from the parent process for this new purpose.
(This should be about registering console message watcher in this list)
Then, if HttpBaseChannel::LogORBError only runs in the parent process, then DevTools code will intercept the console message right from the parent process and data should not be leaked to the content process.
Otherwise, if that method runs in the content process... then we would need to find a way to somehow make the same logic run in the parent process. Assuming ReportToConsoleByWindowID works in the parent process, it should reach out devtools code listening in the parent process directly.
We could probably coordinate to enable DevTools to listen for console message in the parent process, and you ensure the console message is notified from the parent process?
Description
•