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.

Something I have noticied about Firefox team, it's reporting bugs to them do actually means something. They do put effort to solve them.

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.

That is on our list for sure and some fixes have landed in 74 and 75. More to do for sure, but these issues are a priority in our performance program.

> then manually kill the Chrome tab and I can still run through 1 million console lines smoothly

How does that work with DevTools – closing the tab and reading logs?