Closed Bug 1042761 Opened 8 years ago Closed 8 years ago

onResponse is not a function at dbg-client.jsm:1670


(DevTools :: Debugger, defect, P2)



(Not tracked)

Firefox 34


(Reporter: past, Assigned: past)



(1 file, 1 obsolete file)


1. Open the debugger in
2. Open the events pane and choose to break on click events.
3. Click in the input box and then clear the break-on-click checkbox.
4. The Browser Console contains the error: onResponse is not a function at dbg-client.jsm:1670

Patch forthcoming.
Priority: -- → P2
Fortunately this bug doesn't break anything for me, because the error is thrown in a setTimeout call, so the event loop is empty. I've looked around in the debugger client and there are a number of other cases where we assume the caller will supply a callback that I also fixed.
Attachment #8460968 - Flags: review?(rcampbell)
Rather than repeating `() => {}` everywhere, can we just define `const noop = () => {};` and use that?
Good idea, but used let instead of const, because there was a redeclaration error that I didn't want to figth with.
Attachment #8460978 - Flags: review?(rcampbell)
Attachment #8460968 - Attachment is obsolete: true
Attachment #8460968 - Flags: review?(rcampbell)
Attachment #8460978 - Flags: review?(rcampbell) → review+
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 34
QA Whiteboard: [qa-] → [good first verify]
Panos Astithas, could you please add another test page? The one from comment 0 seems to not be available. Thank you
Flags: needinfo?(past)
It seems to be moved here:
Flags: needinfo?(past)
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.