Firefox code inspector hangs when trying to investigate elements


(Alex) #1

The inspector opens, but the element you are trying to inspect did not show up, it shows only head and body tags. Example site:
https://ldsreflections.com/

Firefox Quantum 59.0.2, Win8

Please help!


(Patrick Brosset) #2

Hi. I tested on Firefox 59 and 60, both on Windows 10, and didn’t have the same problem. The elements appeared correctly.

One thing that might help is if you ever run into this again, check into the browser console (ctrl+shift+J) to see if there are any errors in there that appear as you try to inspect an element.

Hopefully, this helps resolve the issue.


(Mike Ratcliffe) #3

I can reproduce this in Developer Edition (60.0b8) on OSX.

I see various errors in the browser console:

TypeError: currentPanel is undefined
Stack trace:
destroyInspector/this._destroyingInspector<@resource://devtools/shared/base-loader.js -> resource://devtools/client/framework/toolbox.js:2629:1
_run@resource://devtools/shared/base-loader.js -> resource://devtools/shared/task.js:310:39
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:928:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:812:7
scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:748:11
Full Message: TypeError: panel is undefined
Full Stack: onLoad/<@resource://devtools/shared/base-loader.js -> resource://devtools/client/framework/toolbox.js:1753:13
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:928:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:812:7
scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:748:11
Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://www.youtube.com’) does not match the recipient window’s origin (‘https://ldsreflections.com’).

(Mike Ratcliffe) #4

Works fine in nightly 61.0a1 (2018-04-03)


Firefox is removing DOM elements from inspector
(Mike Ratcliffe) #5

This could be related to Firefox is removing DOM elements from inspector


(Matthew Jonat) #6

Has there been any progress on this? I find it incredibly frustrating but really like Firefox developer edition and dont really wanna switch back to chrome.

I can give more information about my work environment but I I still have no idea what is causing it although it seems to happen more often when I am working in responsive design mode.

This issue was happening at work on a mac although now I work from home in Linux…apart from both operating systems being unix based the only other thing thats the same is my dev environment using webpack and browsersync to serve the sites. At home I have no plugins on firefox so it isnt a plugin causing the issue.

If there’s any other logs or anything you need me to provide I will.