4 ms·
Did exactly this, a few weeks ago. Was heavy Chrome user, now fully on Firefox (and Safari on mobile). I am so satisfied with this decision, and the transition
by Slartie 8y ago
Did exactly this, a few weeks ago. Was heavy Chrome user, now fully on Firefox (and Safari on mobile). I am so satisfied with this decision, and the transition was much easier than expected.
- fareesh 8y agoI would do it instantly if the devtools were half as convenient as Chrome. Unfortunately they are super clunky
- martin_a 8y agoWhat are you missing? I was feared of this too, but they seem to be just fine.
- chillydawg 8y agoCan't inspect websocket frames. It's ridiculous.
- martin_a 8y agoI'm out of that, but maybe somebody else in here got an idea how to fix your problem with that.
- chillydawg 8y agoMy solution is to use chrome when faced with that particular limitation. There's a bug open on the mozilla tracker and it's been there for a while but no one seems to care.
- askmike 8y agoWhile I run into this too from time to time, it's not something everyone uses. Also it takes me 5 seconds to workaround by debug logging incoming ws messages. Most web devs I talk to can do everything with FF devtools more than fine.
- BorRagnarok 8y agoI use both, Chrome for client side dev, Firefox for everything else. Chrome is just the dev tool. Works like a charm because switching between tabs inside a browser is just as quick as alt-tabbing between browsers.
- kreetx 8y agoI use them all the time, don't seem clunky to me. What else is not working other than the websockets inspection you mentioned?