Open Bug 1036699 Opened 11 years ago Updated 2 months ago

Visually differentiate between sourcemapped or prettified source in our tools

Categories

(DevTools :: General, enhancement, P3)

30 Branch
x86
macOS
enhancement

Tracking

(Not tracked)

People

(Reporter: canuckistani, Unassigned)

References

(Blocks 1 open bug)

Details

There isn't really a way to tell if something in the style editor or debugger has been loaded via sourcemap, has been prettified, or is the original source.
A prettified source in the debugger would have the 'Prettify source' button depressed, but I agree with your general point.
(In reply to Panos Astithas [:past] from comment #1) > A prettified source in the debugger would have the 'Prettify source' button > depressed, but I agree with your general point. That's true in that specific case but for sourcemaps or prettified css code we don't do anything. If we're going to indicate this status ( 'this file is exactly as loaded from disk' vs 'this is a more readable version of the file' ) we should be consistent. It'd be especially helpful for sites where an 'all.js' links back to a number of source files.
Blocks: source-maps
Priority: -- → P3
Severity: normal → enhancement
Product: Firefox → DevTools
Severity: normal → S3

Bug 1853899 made it clear for JS sources in the debugger, by adding a menu and a label to distinguish original versus bundles.

Depends on: 1853899
You need to log in before you can comment on or make changes to this bug.