Open Bug 1601275 Opened 5 years ago Updated 3 years ago

Breaking on DOM mutations from the OBT in the content page does not fully work

Categories

(DevTools :: Debugger, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: pbro, Unassigned)

References

(Blocks 3 open bugs)

Details

Steps:

  • Open google.com in Firefox
  • Open the OBT
  • In the inspector, pick the Google Applications button (it's in the top right hand side corner of the content page, and looks like a square with 9 smaller squares inside of it)
  • Right click on the selected node and choose "break on attribute modification"
  • In the content page, click on that icon

Expected:

  • the OBT should switch to the debugger,
  • the pause overlay should be shown
  • the right thread should be selected
  • the right script should be selected
  • the debugger should be in pause state

Actual:

  • the OBT switches to the debugger
  • the pause overlay appears over the content area
  • but neither the thread nor the script get selected in the debugger, and the debugger is not in paused state.

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)
Priority: -- → P3
Whiteboard: dt-fission-m2-reserve

Tracking for Fission Nightly (M6)

Fission Milestone: --- → M6

dt-fission-m2-reserve bugs do not need to block Fission Nightly (M6). For now, let's track them for Fission riding the trains to Beta (M7) so we revisit these bugs before we ship Fission.

Fission Milestone: M6 → M7

Bulk move of all dt-fission-m2-reserve bugs to Fission MVP milestone.

Fission Milestone: M7 → MVP
Whiteboard: dt-fission-m2-reserve → dt-fission-m3-mvp

Still failing on latest central, but the actual results changed. Now nothing happens.

Severity: normal → S3
Flags: needinfo?(jlaster)

Interestingly, it seems to work fine on remote frames.

Debugger breaks as expected.

See Also: → 1687296
Whiteboard: dt-fission-m3-mvp
Fission Milestone: MVP → ---
You need to log in before you can comment on or make changes to this bug.