1026547 - Show chrome source on about: pages in the debugger

Status: RESOLVED DUPLICATE of bug 1085446

(DevTools :: Debugger, defect)

Description

[Gregg Lind (Fx Strategy and Insights - Shield - Heartbeat )]

Use case:  debugging `about:newtab`.

Reproduce:
- Aurora 32
- `about:newtab`
- open debugger

Expected: debugger should see:  http://mxr.mozilla.org/mozilla-central/source/browser/base/content/newtab/newTab.js  as a source.

Observed: Debugger states:  "no sources".  Inspector has access to objects in the page from that script, including `gSearch`.  

Suggested previous solution of "use the browser debugger" doesn't seem to work for this.  The browser debugger debugs `browser.xul`.

Comment 1

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

If you reload, does the source show up? If so, this is a duplicate of bug 944258.

Comment 2

[Gregg Lind (Fx Strategy and Insights - Shield - Heartbeat )]

No.  "waiting for sources" briefly displays, then "This page has no sources".  I think it's pretty reproducible, if you want to try it.

Comment 3

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

Can repro on Nightly 33 as well.

Comment 4

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

In my opinion all scripts included by about: pages should be available in the debugger if an about: page is loaded.

Comment 5

[Panos Astithas (he/him) [:past] (please ni?)]

The reason debugging about: pages doesn't work (see _allowSource in script.js) is that the debugger would end up running with debuggee frames on the stack. Since Shu recently made that a workable situation, maybe we could now revisit this.

That said, I can debug newTab.js using browser debugger just fine. For example I can set a breakpoint in Page_init() that gets triggered when I hide/show the thumbnails.

Comment 6

[Panos Astithas (he/him) [:past] (please ni?)]

Bug 1085446 fixes this.