forked from mirrors/gecko-dev
c6f171a8b1
`WebConsoleConnectionProxy` is now only used for: - listening to `lastPrivateContextExited`, which can be done from the top-level console front instead - setting `NetworkMonitor.saveRequestAndResponseBodies` for toolbox we don't have network resource support for, which would be better done in `startWatchingNetworkResources`. This means we don't need to keep a Map of additional proxies. The only impact is on `clearMessagesCache`, where we now fetch all fronts with `getAllFronts` instead of looping through the Map of additional proxies. This change highlighted some race condition in tests, as it's now slightly slower. So we add a new `clearMessagesCacheAsync` function, which is doing the same thing as `clearMessagesCache`, except it's not `oneway`, so we can know when the cache was indeed cleared, and we emit an event to indicate when the cache was cleared. We can't simply remove `oneway` from `clearMessagesCache` as it causes backward compatibility issues we can't avoid. This also highlighted an issue with the cache not being cleared on `console.clear` when it is batched, so we fix this (a test was failing without it). The next patch in the queue will completely remove `WebConsoleConnectionProxy`. Differential Revision: https://phabricator.services.mozilla.com/D150085 |
||
|---|---|---|
| .. | ||
| console_messages | ||
| helpers | ||
| invoke_getters_from_autocomplete | ||
| remoting | ||
| rich_output | ||
| split_console | ||
| the_command_line_interpreter | ||
| ui_tour | ||
| index.rst | ||