jasonlaster11

9 ms·

31.
by jasonlaster11 7y ago
The plan is to do user testing on mac and if it is validated roll it out. Replay requires a ton of difficult platform-level investment to get right and we're still actively finding bugs in the real world. After it is validated, it will
32.
by jasonlaster11 7y ago
Good question. Everything is in firefox and open source Here are the bugs: https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&na... Here's the primary directory: https://searchfox.org/mozilla
33.
by jasonlaster11 7y ago
From a user perspective, we are trying to focus less on rewind and step back and more on adding logging retroactively. The best way to think about this is when the user adds a logpoint, they'll immediately see the logs in the console.
34.
by jasonlaster11 7y ago
Thanks for sharing!
35.
by jasonlaster11 7y ago
Thanks for the feedback! 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 th
36.
by jasonlaster11 7y ago
Hmm, join us in http://devtools-html.slack.com/ and we'd be happy to help you debug it. If the tab crashed, you can get the report in about:crashes
37.
by jasonlaster11 7y ago
Firefox Replay supports MacOS while we're validating the feature. When it comes time to plan for releasing replay we'll work on cross-platform support. Unfortunately, Replay hooks into low-level OS system calls to do the recording
38.
by jasonlaster11 7y ago
Thanks for the feedback! Our #1 use-case at the moment is bug reports with a recording attached. We think that will really help when it comes to understanding the specifics of a bug when STRs are often not clear.
39.
by jasonlaster11 7y ago
That's right. The only way to have a performant recording is to capture the browser's OS system calls in the recording. This unfortunately makes the feature quite OS specific. https://searchfox.org/mozilla-central&
40.
by jasonlaster11 7y ago
Team member here. Firefox Replay is currently in user research phase while we validate it. Cross platform support will absolutely be a priority when Replay is on the official roadmap. Thanks for the feedback, firefox-replay.com is also a wo
41.
by jasonlaster11 7y ago
That's exactly right 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 re
42.
by jasonlaster11 7y ago
Hi, Firefox DevTools Debugger engineer here. We've focused on performance and quality over the past six months and believe it should be much better. If you're still seeing issues, feel free to record a performance profile and send
43.
by jasonlaster11 7y ago
Happy to discuss collaborating on mapping variables. The current approach is based on re-parsing with babel, but we would like to extend source maps to include relevant mapping data. https://twitter.com/auchenberg/statu
44.
by jasonlaster11 8y ago
That's a great point. Tracing quickly becomes slow and memory intensive. I think you would enjoy this write-up. WebReplay is explicitly not tracing for that reason. https://developer.mozilla.org/en-US/docs/Moz
45.
by jasonlaster11 8y ago
The problems I see with limiting the scope to single function IO are 1. JS is dynamic and a single function can do a lot, even if you try to stub out the world. 2. from a product perspective it would be hard to communicate what is going on.
46.
by jasonlaster11 8y ago
Thanks for sharing the link. I'd like to emphasize that webreplay is still R&D :) It is neat to see how far we've come in a year though!
47.
by jasonlaster11 8y ago
We'd love to. We have a WIP patch. At the moment, we're prioritizing MVP functionality, performance, and stability.
48.
by jasonlaster11 8y ago
We're making progress on an experimental version in Firefox DevTools. It's not on the roadmap, but it is easy to try and we'd love feedback. https://developer.mozilla.org/en-US/docs/Mozilla/Proj
49.
by jasonlaster11 8y ago
That's amazing!
50.
by jasonlaster11 8y ago
Yep. It's on the roadmap, but the recording is done at the OS level, so Windows and Linux will require some work to get support.
51.
by jasonlaster11 8y ago
Here are some docs on how to try it in nightly. https://gist.github.com/jasonLaster/1e220992c294a571dd9b59ab...
52.
by jasonlaster11 10y ago
yep - at the time we were not sure if we would want to transpile the code.
53.
by jasonlaster11 10y ago
Thanks! We'd love to have OSS help. We try to be as beginner friendly as possible. Getting started is as easy as `npm install; npm start`. Here are our contributing docs - https://github.com/devtools-html/debugger
54.
by jasonlaster11 10y ago
I like that idea. I think we can do several things when it comes down to tracking changes: * make it easier to pause when a reference is set/get * make conditional breakpoints more of an every-day experience * better symbol search so t
55.
by jasonlaster11 10y ago
Thanks for the feedback. (project maintainer) I agree that "live edit" is an exciting feature. It supports a tighter feedback loop that lets you iterate in the correct context. There are two challenges 1. transpiling, which would
56.
by jasonlaster11 10y ago
We're working on a new Firefox debugger wtitten in react-redux, which we hope will be a platform for prototyping interactive/visual features. https://github.com/jlongster/debugger.html
57.
by jasonlaster11 12y ago
Thanks! This is a cool concept. It's interesting in that it helps pull in projects in a way that seems similar to package managers like npm, bower, bundler...
58.
by jasonlaster11 12y ago
same!
59.
Improve Your Backbone Views with Marionette Behaviors(github.com)
6 points by jasonlaster11 13y ago|0 comments
60.
by jasonlaster11 13y ago
Would be great as a chrome extension

More ›