Closed Bug 1611418 Opened 4 years ago Closed 4 years ago

SourceMapURLService originalPositionFor should return null when sourcemaps are disable via prefs

Categories

(DevTools :: Framework, defect)

defect
Not set
normal

Tracking

(firefox74 fixed)

RESOLVED FIXED
Firefox 74
Tracking Status
firefox74 --- fixed

People

(Reporter: rpl, Assigned: rpl)

Details

Attachments

(1 file)

What happened?

During the Bug 1609671 review Julian noticed that SourceMapURLService is only checking the "devtools.source-map.client-service.enabled" preference for its "event-based" API but not for originalPositionFor.

What should have happened?

As Julian pointed out in his review comment, we can either:

  • 1/ return null in originalPositionFor if the preference is false (we are already tracking it inside the module via _prefValue)
  • 2/ review with @Harald if the option "Enable Source Maps" still makes sense to be exposed or if we should just always enable source maps now

Anything else we should know?

I'm going to attach a patch for the option 1 (and include an additional test case to cover the scenario for the inspect binding, in addition to the one added in Bug 1609671), if instead we are going to remove the pref sooner, this issue can be resolved as "wontfix".

Summary: SourceMapURLService originalPositorFor should return null when sourcemaps are disable via prefs → SourceMapURLService originalPositionFor should return null when sourcemaps are disable via prefs
Assignee: nobody → lgreco
Status: NEW → ASSIGNED
Attachment #9122870 - Attachment description: Bug 1611418 - SourceMapURLService originalPositorFor should return null when sourcemaps are disable via prefs. r?jdescottes! → Bug 1611418 - SourceMapURLService originalPositionFor should return null when sourcemaps are disable via prefs. r?jdescottes!
Pushed by luca.greco@alcacoop.it:
https://hg.mozilla.org/integration/autoland/rev/80b669e25635
SourceMapURLService originalPositionFor should return null when sourcemaps are disable via prefs. r=jdescottes
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 74
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: