[Feature] Include websocket frames in the trace-viewer

[Bessonov]

Hey guys! Playwright is amazing and thank you very much for it!

I rely heavily on WebSockets and it would be nice if they could be included in the trace viewer.

[mxschmitt]

web-socket traffic is often binary or JSON based - what kind of data are you sending? Having the JSON of the request and response frames visualised would be also required then.

[Bessonov]

My use case is exclusively json based

[unlikelyzero]

This would be amazing for us as well!

Ultimately our team has chosen playwright over Cypress for many reasons, but websocket "support" is one of them.

[Oscaruzzo]

+1 on this. We have some websocket traffic (push notifications, mainly, plus some relatively small data, all json based) and it would be REALLY useful to include this in traces.

[Sysqwerty]

Hi guys. Same for our team. It would be really cool to have WebSockets logs in the Trace report. Our application uses WS for a bunch of functionalities through all the system.

Hi, @mxschmitt, do you plan to implement it? (I see the ticket is open more than 1.5 years ago)

[nicolasgarfinkiel]

+1 and I wouldn't mind taking a stab at adding this info to the viewer if no one is working on it.

[mofojed]

This would be handy. Note you can print out WebSocket frames that are sent/received to the console: https://playwright.dev/docs/network#websockets Having it in the Network tab would be much more convenient though. One thing I can't get from the above API is the CloseEvent when the websocket is closed - Playwright just returns the WebSocket on close, I'm not sure how to get the information of that CloseEvent: https://developer.mozilla.org/en-US/docs/Web/API/WebSocket/close_event

[snackattas]

Also ➕ 1️⃣ to this

[amalsgit]

+1

[AAAver]

+1

[serhatgemici]

+1

[satyamsi]

+1

[ulrichstark]

+1