Firefox Replay
171–180 of 297 posts
Re: Firefox Replay
#172Re: Firefox Replay
#173Earlier quoted context omitted.
I recently switched back to FF after many years on chrome and find the dev tools to be as good of not better this time around. Curious which tools in particular you find worse? When was the last time you tried?
You know, as I'm going back and trying to come up with specific points, I'm having a hard time. Partly it's little usability things: - There was one time when an HTTP request was failing and I couldn't figure out why, and in the Network tab Firefox wouldn't show any information about it, even the request that went out (other than the URL), whereas Chrome not only showed the headers, it surfaced that it was a 404. - T…
Lately though I haven't found myself needing to switch over to Chrome for anything devtools related. This new replay feature makes FF even more compelling (once it comes to Linux that is).
So if you haven't used FF for development recently, you should definitely give it a try.
Re: Firefox Replay
#174Re: Firefox Replay
#175I am not primarily a web developer, but I guess I don't really see it. I suppose 'rewind' would mostly be useful for Javascript applications? But in Javascript you can already debug pretty well. It's been a while, but I suppose Javascript debuggers can drop frames, like debugging other languages, so you already have a kind of rewind? Does anyone have a good example use case for this?
This video has a good intro: https://www.youtube.com/watch?v=ytNlefY8PIE
Re: Firefox Replay
#176As a former gnu/linux user, I see no point to have it on a desktop. Gnu is happy to live under c:/MSYS2, and ‘linux’ part was never good at desktop-home hardware anyway. These 1.77% are barely justified as an option, imo.
After struggling with GPU drivers, again, the last couple of days, I could not agree more!
Re: Firefox Replay
#177Earlier quoted context omitted.
You know, as I'm going back and trying to come up with specific points, I'm having a hard time. Partly it's little usability things: - There was one time when an HTTP request was failing and I couldn't figure out why, and in the Network tab Firefox wouldn't show any information about it, even the request that went out (other than the URL), whereas Chrome not only showed the headers, it surfaced that it was a 404. - T…
FF's tools used to be pretty bad compared to Chrome's, and while my main browser has always been FF I always keep Chrome around for development purposes. Lately though I haven't found myself needing to switch over to Chrome for anything devtools related. This new replay feature makes FF even more compelling (once it comes to Linux that is). So if you haven't used FF for development recently, you should definitely giv…
Re: Firefox Replay
#178Earlier quoted context omitted.
You can't talk about Chrome's market share without mentioning that it was (maybe still is? I don't know) prominently advertised on the google.com homepage. Everyone who went to search Google saw the ad. It said something like "Try a faster browser" The fact that Chrome was advertised on the most popular page in the world, and especially that it was the only ad on that page, definitely made a difference in adoption. T…
Source? I don't remember such an ad. Speaking as a dev, the dev tools had a ton to do with it.
There’s also a popover div ad in gmail: https://twitter.com/ridiculous_fish/status/10810743891336806...
Re: Firefox Replay
#179As a former gnu/linux user, I see no point to have it on a desktop. Gnu is happy to live under c:/MSYS2, and ‘linux’ part was never good at desktop-home hardware anyway. These 1.77% are barely justified as an option, imo.
Re: Firefox Replay
#180It might just be me but enabling the option and clicking and the recording button just attempt to reload the page and I get a blank page. Not sure what is supposed to happen.