by nachtigall on 11/28/19, 9:59 AM with 286 comments
by darshan on 11/28/19, 8:26 PM
This currently has 1215 points, and the link is no longer valid. It now just shows an image of Firefox's devtools and the sentence "Replay is an early experiment. We'll let you know on @FirefoxDevTools when it's ready for input." That's not useful, interesting, or informative. The MDN docs seem like an appropriate replacement.
by inglor on 11/28/19, 10:51 AM
``` // 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: intra-thread and inter-thread.
// Intra-thread non-deterministic behaviors are non-deterministic even in the
// absence of actions by other threads, and inter-thread non-deterministic
// behaviors are those affected by interleaving execution with other threads.
```
by strombofulous on 11/28/19, 10:14 AM
Firefox definitely managed to catch up but not before lots of devs switched to chrome and stopped checking for compatibility with Firefox.
by Roark66 on 11/28/19, 11:28 AM
What is the point of promoting this to everyone at this stage?
by Etheryte on 11/28/19, 12:23 PM
I can't quite remember when I had a bug where a tool like this would've been useful, but I'm sure I would've been (and will be) very thankful for it.
by devit on 11/28/19, 10:14 AM
Is it not supported on Linux and Windows? Why?
by jasonlaster11 on 11/28/19, 6:59 PM
Replay is in the user-research and validation phase and still quite experimental.
firefox-replay.com is a work in progress. We're still sorting out the best way to communicate record and replay debugging and the new use cases.
We'll share more on @firefoxDevTools when we have something to report.
by ihuman on 11/28/19, 7:12 PM
"Replay is an early experiment. We'll let you know on @FirefoxDevTools when it's ready for input."
by kevsim on 11/28/19, 10:19 AM
by tenryuu on 11/28/19, 12:22 PM
A new option in settings will be added to enable a Toolbox Button named "Enable WebReplay", but pressing that button will replace the entire tab content with an about:blank
by danShumway on 11/28/19, 2:36 PM
I'm pretty happy to see Firefox pushing its dev tools in this direction. They've done a really great job with layout and styling tools, but their JS dev tools have lagged behind Chrome's. So even if this particular effort doesn't pan out for some reason, it's still very encouraging.
They're not just carbon-copying Chrome, and they're not just sitting back and ignoring the dev tools; they're trying to push them forward in some interesting ways.
by inglor on 11/28/19, 10:39 AM
by mattfrommars on 11/28/19, 6:27 PM
[Link to the editor](https://github.com/abdusamed91/realtime-codeeditor)
I implemented it in my real time code editor coursework project where I made use of [Ace Editor](https://ace.c9.io/)'s CRDT. The time machine slider does the job and looked remarkable when it ran.
by brna on 11/28/19, 10:40 AM
by ga-vu on 11/28/19, 10:44 AM
by saimiam on 11/28/19, 10:34 AM
1. I installed the nightly build as told.
2. Open nightly build
3. Went to the "Save Recording" option
4. The first two times, I got a [javascript error] saying I could not record.
5. The remaining couple of times - after I open a "New Recording Tab", whatever that is - I didn't see the javascript error but the website whose clickthru I wanted to record using this tool didn't even load in that new recording tab.
Just this morning I recorded a clickthru like caveman using Quicktime. Can't wait for FF to iron out the kinks in this feature.
by sdan on 11/28/19, 11:16 AM
To be clear, I use both Chrome and Firefox for development but just to the surface level, so I'm probably missing the point here.
by ManlyBread on 11/28/19, 11:26 AM
by swsieber on 11/28/19, 9:24 PM
I had built a poor mans version of this where I worked with puppeteer for automated tests. It'd basically record the full dim any time it changed, along with console logs, network request metadata, images and css and output it as a test recording. You could then view that and walk through it in an Electron app.
This'll blow it out of the water. I hope for e2e testing's sake that linux support comes soon.
by empressplay on 11/29/19, 12:06 AM
[1] https://paleotronic.com/software/microm8/help/web-debugger/
by Blaiz0r on 11/28/19, 10:18 AM
Does Replay work on the Firefox Dev build?
by asaddhamani on 11/28/19, 12:28 PM
by aedron on 11/28/19, 11:48 AM
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?
by Karupan on 11/28/19, 10:29 PM
I’m going to give this a shot today!
by foobaw on 11/28/19, 6:59 PM
by jv22222 on 11/29/19, 2:34 AM
by hyt7u on 11/28/19, 5:09 PM
by jrm2k6 on 11/28/19, 3:38 PM
by 8bitsrule on 11/28/19, 6:34 PM
Strange days indeed. Just giving some thanks where it's due.
by mimischi on 11/28/19, 10:37 AM
by Abishek_Muthian on 11/28/19, 2:13 PM
by deedree on 11/28/19, 4:56 PM
by shepardrtc on 11/28/19, 5:03 PM
by meerita on 11/28/19, 7:44 PM
> An error occurred when connecting to firefox-replay.com. PR_CONNECT_RESET_ERROR
by smnrchrds on 11/28/19, 3:31 PM
by markdog12 on 11/28/19, 1:37 PM
by softwarelimits on 11/28/19, 12:22 PM
by OrgNet on 11/29/19, 4:27 AM
by kyriakos on 11/28/19, 6:34 PM
by bogwog on 11/28/19, 4:15 PM
by wruza on 11/28/19, 12:10 PM
by sandGorgon on 11/28/19, 10:54 AM
by Shaaaaaaare on 11/28/19, 11:03 AM
by bdibs on 11/28/19, 10:21 AM
by _bxg1 on 11/28/19, 3:21 PM
by inglor on 11/28/19, 10:40 AM
Would people be interested in us open sourcing that part for regular debugging? I have considered it but I didn't think people would be interested in using this in a non-test case.
by aphroz on 11/28/19, 11:05 AM