4 ms·
Wish I didn't have to open Chrome to view websocket frames though. Firefox does detect that a WS connection was made, it just can't inspect it.
by wyattjoh 9y ago
Wish I didn't have to open Chrome to view websocket frames though. Firefox does detect that a WS connection was made, it just can't inspect it.
- a_humean 9y agoThis is also a big barrier for me using firefox in development, and pre-v57 Firefox used to have an extension for websockets that was nice, but its gone now with the new web extension APIs.
- vanderZwan 9y agoI have a similar thing but with profiling JS performance: if you profile a page in Chrome and then inspect the source code, it gives estimates of seconds spent per line of code. Firefox does not have this. Being able to detect which function is the bottleneck is great, but being able to then figure out where the time is spent inside that function can be very enlightening too.
- robin_reala 9y agoThat‘s being worked on in Q1: https://news.ycombinator.com/item?id=15695910 https://news.ycombinator.com/item?id=15695910