Closed
Bug 905863
Opened 11 years ago
Closed 1 year ago
Implement a blackbox source map directive
Categories
(DevTools :: Debugger, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1824705
People
(Reporter: fitzgen, Unassigned)
References
(Blocks 3 open bugs)
Details
These would be ordered indices into the `sources` list and parsed `mappings` property respectively. For example, { sources: ["foo.js", "bar.js", "blackboxed.js"], xBlackBoxedSources: [0, 2], // rest of the source map } would say that "foo.js" and "blackboxed.js" should be black boxed by default. We could do the same thing for the mappings, although we wouldn't really have any UI to turn the black boxing off, so it would be pretty permanent.
Comment 1•11 years ago
|
||
I suggest `xBlackBoxedSources: { 0: "backbone", 2: "backbone" }` so that multiple sources could be grouped into a single checkbox in the UI?
Comment 2•11 years ago
|
||
I'm not a huge fan of adding blackboxing from the (web) server without a way to disable that in our tools. The idea of having a single checkbox to turn off all xBlackBoxedSources is a nice suggestion.
Reporter | ||
Updated•11 years ago
|
Priority: -- → P3
Updated•10 years ago
|
Blocks: dbg-blackbox
Updated•10 years ago
|
Summary: Extend the source map format with xBlackBoxedSources and xBlackBoxedMappings → Implement a blackbox directive for source maps
Updated•10 years ago
|
Summary: Implement a blackbox directive for source maps → Implement a blackbox source map directive
Updated•10 years ago
|
Blocks: dbg-sourcemap
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•5 years ago
|
Type: defect → enhancement
Updated•2 years ago
|
Severity: normal → S3
Updated•1 year ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•