Open Bug 1581565 Opened 3 years ago Updated 4 months ago

The React extension confuses breakpoints in HTML files

Categories

(DevTools :: Debugger, defect, P2)

defect

Tracking

(Not tracked)

People

(Reporter: jlast, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [debugger-reserve])

STR:

  1. go to http://janodvarko.cz/xhr-spy/
  2. add a breakpoint in xhr-spy/(index) on line 80
  3. refresh

ER:

  • pause on 80
  • see the breakpoint in the editor and panel

AR:

  • pause
  • file does not load
  • breakpoint does not appear in the panel
Blocks: dbg-71
Priority: -- → P1

Brian, could you look into this?

Assignee: nobody → bhackett1024
Flags: needinfo?(bhackett1024)
Whiteboard: [debugger-mvp]

I just tried this a couple times on autoland tip and can't reproduce it. How often does this happen for you?

here's a quick video -- https://www.loom.com/share/ce651fbe535344058c04e71f8bc6b684

it requires react devtools to be installed

it looks like loadSourceText works, so not sure where it is failing yet, but the server seems fine

I was able to reproduce a problem immediately after installing React DevTools add-on. No Firefox Restart, no Toolbox reopen.
But, slightly different observation:

  • The BP icon in the gutter disappeared
  • The BP was still hit
  • The BP was not in the list of BPs (in the side panel)
  • I can see the source

(Cache disabled in the Network panel)

There must be some racing since it's hard to reproduce again.

Honza

Priority: P1 → P2
Whiteboard: [debugger-mvp] → [debugger-reserve]

lowering the priority because it requires several things to be true (react addons, disabled cache, and html files)

Flags: needinfo?(bhackett1024)
Assignee: bhackett1024 → nobody
Summary: "disabled cache" confuses breakpoints in HTML files → The React extension confuses breakpoints in HTML files

This seems to work for me on Nightly, Jason could you verify?

Flags: needinfo?(jlaster)
Flags: needinfo?(jlaster)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.