I use Chrome to benchmark my local version of a website. The use case is very limited, because the results fluctuate a lot depending on the overall load on my machine (including the dev server), so I usually do three passes on the master branch of my project, get scores like 53, 56, 51, then switch to my development branch, three passes again, if I see e.g. 58, 56, 61 then it's fine, if the results are noticeably lower than master then time to investigate.
In any case we have a dedicated environment with lighthouse-ci and this is where the real pre-release benchmarks are executed.
Very glad to hear that! Now that I know what is going on, I check the console whenever the request doesn't appear in Network tab, but it is very unintuitive. Keep up the good work!
This would be amazing. It's one of the last holdouts of why I develop on Chrome - I need to be able to see the failed request to debug what's getting sent and what isn't!
I am on Nightly which updates 2x daily without problems. If restart doesn't work maybe try a re-install. Filing a bug would be great so Firefox devs can work with you to find a root cause.
On Windows it should background update now as well.
Firefox member here – thanks a lot for reporting those bugs! Thanks to detailed reports Debugger could improve and glitches should become more and more a rarity.
You're welcome. Thanks a lot for your work on Firefox!
Wish I could have reported the breakpoint page refresh bug, but I wasn't sure how I could possibly isolate/replicate or describe beyond what I described above. And that's probably not very useful? The small one I linked was easy to describe and replicate.
Anyway, reporting bugs to Firefox definitely seems worth the time spent because it means having a browser that doesn't exist solely to benefit Google. Long live the World Wide Web!
PS. Really like so many other DevTools details I didn't mention in my post above. For example, the '...', 'scroll' and 'flex' indicators/toggles: https://imgur.com/a/yIlhDcJ. Also the console reverse-search with Ctrl-R. And many others.
Thanks for your work on Firefox!
I feel more comfortable with Firefox Devtools overall, but I keep using Chrome for debugging for one single reason : Firefox can't handle extensive log.
I'm working on code where sometimes infinite loops occurs. When I want to investigate on these loops, I cannot use any breakpoints because it's using the same route than it used 10 000 times before, so I usually log a lot of data, then manually kill the Chrome tab and I can still run through 1 million console lines smoothly.
Really hope Firefox will be able to handle that one day.
Please report those via webcompat.com – Firefox's compat team will always follow up and learn more how to close the platform gap that causes the issues but also reach out to the devs.
