Hacker News Reader

Comment by pfooti | Hacker News Reader

Is there some super-compelling reason why FF doesn't let you inspect websocket frames? I was taking FF for a drive yesterday, based on the earlier thread, and it was nice until I started debugging my web app.

I'm not interested in trusting a third party extension with all my network data either, so the plug-in to do this isn't an option. It's weird, but this really is a blocker for me for general use.

View on HN

Sorry about that inconvenience. The current plan is to revisit WebSocket debugging in Q1 next year, per https://bugzilla.mozilla.org/show_bug.cgi?id=885508.

Part of the delay is the complete rewrite that most of the DevTools are undergoing. As we move from legacy, in-house solutions (XUL) to standard web technology (HTML/JS, React/Redux, etc.) as part of the "devtools.html" project: https://github.com/devtools-html/

I see the tracking issue has been in bugzilla for years. I get that it is a tricky map from the raw packets to these frames, but relying on a 3rd party extension to the point of deprioritizing work on this is a pretty iffy call - I wasn't excited about trusting an extension at all; that the extension seems to have been broken in 57 entirely (foreseeably too) just feels meh.

I guess I'm part of a minority of people who does a lot of websockets work? Well, that's guaranteed to be true - a random feature deep inside the devtools is probably a deal-breaker for like four people.

Very sorry about that. The third party extension was developed by a core DevTools engineer, just not merged upstream. We'll get there. :)

Reply on news.ycombinator.com