IssueTracker

This is a regression in chromedriver from 132 to 133 and affects testing of applications that use a WebSocket of their own. We see this with Cockpit https://github.com/cockpit-project/cockpit. Cockpit uses a WebSocket to transfer commands and data from the browser to the host that it is managing.

When testing Cockpit with chromedriver 133, we see all the traffic that Cockpit sends over its own WebSocket in the "BiDI/CDP Mapper" tab. There are numerous Network.websocketFrameReceived and Network.websocket.FrameSent entries. With chromedriver 132, we only see the commands related to the bidi protocol itself.

The extra Network.websocket* event logging makes the "BiDI/CDP Mapper" tab useless. Also, some of our tests transfer more than a Gigabyte of data over Cockpit's websocket and every byte of it is logged in the BIDI tab. That seems to slow down the bidi protocol enough to cause our tests to timeout when communicating with chromedriver. Chromium consumes a lot of RAM when that happens, to the point that it sometimes gets killed by the OOM killer.

Screenshot attached that shows the new Websocket events.