Firefox Replay
181–190 of 297 posts
Re: Firefox Replay
#182Earlier quoted context omitted.
People on HN don't like anything.
Speaking of which, I'm a little shocked to see a Mozilla thread that doesn't yet mention Pocket or the rebranding or DoH. That must mean we are in a good mood?
Re: Firefox Replay
#183Maybe once they figure out how to monetize the data
When Chrome does add this capability(strange they haven't added it to date given the prior art from years ago), I can see it being used by actual devs inside Google and thus being actually useful.
Contrast that with Firefox dev tools which seem to fall behind the priority list compared to new shiny flashy tech projects they concoct.
Re: Firefox Replay
#184Re: Firefox Replay
#185Very cool, but I'd much prefer they spend their time bringing Firefox's dev tools up to par with Chrome's first. I've tried several times to switch to FF completely, but every time I end up switching back on my work computer because of the dev tools.
Curious to hear what's missing. I do some light front-end work (css/react) and have been fully on Firefox for about a year. Haven't looked back.
Re: Firefox Replay
#186This is a pretty nice comment from the source that explains how it works: https://github.com/mozilla/gecko-dev/blob/11d9c7b7fa82fdfb8a... ``` // Recording and replaying works by controlling non-determinism in the browser: // non-deterministic behaviors are initially recorded, then later replayed // exactly to force the browser to behave deterministically. Two types of // non-deterministic behaviors are captured: intr…
What is non-determinism in the browser?
It's random numbers, the system clock, data off the internet, and input events from the user.
What it sounds like is that Mozilla has come up with a debugging environment that bottles all that nondeterminism up into a neat little package so that it can replay a specific run of your program any time you want.
Re: Firefox Replay
#187Re: Firefox Replay
#188Earlier quoted context omitted.
Speaking of which, I'm a little shocked to see a Mozilla thread that doesn't yet mention Pocket or the rebranding or DoH. That must mean we are in a good mood?
We're busy prepping to argue about UBI at Thanksgiving dinner.
Re: Firefox Replay
#189This is a pretty nice comment from the source that explains how it works: https://github.com/mozilla/gecko-dev/blob/11d9c7b7fa82fdfb8a... ``` // Recording and replaying works by controlling non-determinism in the browser: // non-deterministic behaviors are initially recorded, then later replayed // exactly to force the browser to behave deterministically. Two types of // non-deterministic behaviors are captured: intr…
Sounds like Mozilla is applying the concepts they developed for their C/C++ debugger, rr ( https://rr-project.org ).
Brian Hackett collaborated early on with ROC. Here are the basic principles of Replay (https://developer.mozilla.org/en-US/docs/Mozilla/Projects/We...).
In a nutshell, replay records Firefox's OS system calls, so that that Firefox can read from the recording when replaying.
Re: Firefox Replay
#190Maybe once they figure out how to monetize the data
Chrome's dev tools are so far beyond the competitions that this joke is a non-starter. When Chrome does add this capability(strange they haven't added it to date given the prior art from years ago), I can see it being used by actual devs inside Google and thus being actually useful. Contrast that with Firefox dev tools which seem to fall behind the priority list compared to new shiny flashy tech projects they concoct…