Tools like OpenReplay and Fullstory already are capable of capturing a scary amount of information. I'm curious how far you could go with this idea without the need to be an extension. What would really be missing?
Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
181–190 of 240 posts
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#182[flagged]
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#183I got really excited before I saw there was no firefox support. Thats a deal breaker for my team :( I really like this idea and if Firefox support was added I would purchase it in a heartbeat.
Professionally I do all of my development in Firefox and only occasionally check that Chrome works
It seems pretty bold move when you consider that V8-based browsers covers 75.5% of the market [1].
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#184Earlier quoted context omitted.
> Why? The most important info was the time at which the error happened (which, for users who were on Windows, was in the bottom right of the screen). Except it isn't in UTC and it doesn't show an offset. Even if you stored the user's timezone, that doesn't mean that's where they were working from.
Or, some users might have hidden the taskbar, or the clock. Or have several screens, and only one of them has the clock...
Users that might customise their system a bit by digging into the settings are usually more inclined to give a detailed report in case they encounter a bug or have a general knowledge of what to look for when requested for some information in my team's experience. Sounds much more like an edge case.
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#185I've been playing with this for a few hours and had similar questions about scrubbing custom tokens or headers from the submitted data. One concern I have about the instant-replay feature is the potential performance implications when monitoring multiple tabs or windows. I'm not particularly fond of the idea of all sites in this way and prefer better controls there. I saw the block list inside the extension, but I th…
I think the reason for having the permissions for all sites is for when you want to use the instant replay feature on the off chance and you realise that there were no permissions enabled for the specific domain.
I'd be pretty annoyed if the bug is not reproducible and I lose that chance of generating a bug report.
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#186Earlier quoted context omitted.
Maybe scrub cookies and authorization headers by default, but make them an opt-in for bugs where they're relevant? Edit: it looks like this is already the case!
> but make them an opt-in for bugs where they're relevant? The tool seems to be built for people who don't know what to include in a proper bug report (As they are maybe not technical enough), so not sure how helpful that choice would be for them.
This might be a feature fit for the pro tiers. I would really like it for our QA testers who'd want to include that information but still aren't that technical to know all the places to look for that information.
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#187Earlier quoted context omitted.
Indeed, that's a great rule. Another one is "What URL was the browser on?" which is rarely ever in cropped screenshots but is visible in full screenshot
Don’t many browsers hide the full URL now?
Desktop Chrome only hides the scheme by default I think.
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#188Earlier quoted context omitted.
Professionally I do all of my development in Firefox and only occasionally check that Chrome works
It seems pretty bold move when you consider that V8-based browsers covers 75.5% of the market [1]. [1]: https://gs.statcounter.com/browser-market-share
How is it a bold move? If it works in Firefox it’s much more likely to work in other browsers, whereas if it works in Chrome it might or might not work elsewhere. I switched to Firefox as my default for development years ago because I got fed up of wasting time on issues because something would work in Chrome but not work in one or more other browsers. Using Firefox saves me time and effort so there’s nothing bold about it, purely pragmatic.
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#189Also ex-Cloudflare, have been following Jam for awhile, great product! Something I would love is a way for customers to use this without having to install a Chrome extension. It would make debugging customer issues much faster - for example, if clicking 'Report a bug' on a website automatically triggered the recording flow and asked the user to reproduce it.
+1 on this request.
Would also like to be able to kick a report off automatically -- eg, on any exception or on any 4XX from the server.
Re: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
#190> but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took Ah ah. At one gig we had trained the users to always send a screenshot of the entire screen. People reviewing the tickets would dump them if the screenshot was cropped and the user warned: "No full screenshot, no ticket" . Why? The most important info was the time at which the error happened (…
> Why? The most important info was the time at which the error happened (which, for users who were on Windows, was in the bottom right of the screen). Except it isn't in UTC and it doesn't show an offset. Even if you stored the user's timezone, that doesn't mean that's where they were working from.
The user not being in the time zone we expected has been exactly the information we were missing to debug something more than once. “The logs say it was 10am but the screenshot says 11… what if we were mishandling timezones?”