We should explain the benefits of sourcemaps, and when they're not available #2444
Replies: 2 comments 1 reply
-
The main issue I see with that is that sourcemaps are per-file, so you could have some random file in your page that happened to have sourcemaps, even though none of the scripts you care about actually have them, so treating it as a recording-wide indicator may well be very hit or miss.
Similarly for this, currently at a protocol level we never tell the client about a file until the sourcemap for that file has also loaded. I'm not sure that's strictly required, but I do think some things make that assumption right now, and "loading sourcemaps" is a thing that happens all throughout a recording initial load, since scripts can load onto a page at any time, so you can easily be viewing a recording, even if all of the sourcemaps have not loaded yet.
What we could potentially do is, when the user opens a file that has a |
Beta Was this translation helpful? Give feedback.
-
Hey @loganfsmyth I'm processing our old discussions. Are there any new insights to add to this since it's been a year? |
Beta Was this translation helpful? Give feedback.
-
@jaril and I were discussing how @loganfsmyth is working on manual upload of sourcemaps. This is great.
But it made me realise there are different places in the UI we can bring this to light, both for usability reasons and messaging reasons. Here's what I propose we do:
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions