Closed Bug 986586 Opened 10 years ago Closed 5 years ago

Do something sane when stepping into code into global not shown in the add-on debugger

Categories

(DevTools :: Debugger, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mossop, Unassigned)

References

(Blocks 1 open bug)

Details

The add-on debugger only shows globals from the add-on you're debugging. Sometimes though code execution will flow into something else, a platform piece of JS for example. If you step into a piece of code like this the UI behaves strangely. I think the locals and variables display right but the code doesn't display.

We should do something sane here, either open the code and maybe include it in the list of globals from then on, or just step completely over code that isn't part of the add-on. I think the former is preferable since I suspect we may find a bunch of cases where we don't list everything we need to at first.
Summary: Stepping into code in a global not shown in the add-on debugger should do something sane → Do something sane when stepping into code in a global not shown in the add-on debugger
Summary: Do something sane when stepping into code in a global not shown in the add-on debugger → Do something sane when stepping into code into global not shown in the add-on debugger
Product: Firefox → DevTools

I am not too familiar with the addon-debugger. Is this still relevant?

Flags: needinfo?(dtownsend)

I don't work on add-ons anymore and I have no idea of the state of the add-on debugger.

Flags: needinfo?(dtownsend) → needinfo?(kmaglione+bmo)

Based on comment 0 the issue described seems to be related to the old legacy add-ons, while stepping through WebExtensions code from the addon-on debugger the user cannot reach any platform code.

Thanks luca. I'll mark it as invalid then.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Flags: needinfo?(kmaglione+bmo)
You need to log in before you can comment on or make changes to this bug.