Open Bug 1625418 Opened 4 years ago Updated 4 years ago

Using black box source option many times make the call stack section don’t look the same even after reloading the page

Categories

(DevTools :: Debugger, defect, P3)

defect

Tracking

(firefox74 unaffected, firefox75 affected, firefox76 affected)

Tracking Status
firefox74 --- unaffected
firefox75 --- affected
firefox76 --- affected

People

(Reporter: hyacoub, Unassigned)

References

(Blocks 3 open bugs)

Details

Attachments

(1 file)

Affected versions

75.0b9
76.0a1 (2020-03-26)

Affected platforms

macOS 10.14
Windows 10 x64

What were you doing?

  1. Launch Firefox and go to about:config and set: devtools.debugger.features.async-captured-stacks to true and javascript.options.asyncstack to true.
  2. Navigate to: https://ahfarmer.github.io/calculator/
  3. Press F12 to open the devtools panel and select the "Debugger" tab.
  4. Create BP in ahfarmer.github.io/calculator/static/js/component/Button.js on line 11 (in the render method)
  5. Click a button on the page.
  6. Right click on the content of the call stack and select "Blackbox source".
  7. Repeat step 7 until there is not content in "Call stack" section.
  8. Reload the page.
  9. Make sure the breakpoint is there and click on the page again.

What happened?

Using black box source option many times make the call stack section don’t look the same even after reloading the page.

What should have happened?

Call stack section should be correctly displayed.

The priority flag is not set for this bug.
:jlast, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jlaster)

Thanks for the report!

After reloading the page (step #8) and pausing at the same location (line 11) I can see render in the callstack.
Harald, any input on this?

I agree that blackboxing setup should persist across page reloads, but could be a bit weird if the Callstack panel is entirely empty (no selected frame), when the debugger pauses. Is this a bug?

Perhaps there are more workflow changes needed to get black-boxing UX right?

Honza

Flags: needinfo?(hkirschner)
Blocks: dbg-blackbox
Flags: needinfo?(hkirschner)

P3 as blackboxing is more advanced and our current blackbox reactions need more planning in general.

Flags: needinfo?(jlaster)
Priority: -- → P3

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: