Comments on: DOM Inspector problem

By: Duncan Booth

Duncan Booth — Thu, 07 Dec 2006 13:14:35 +0000

I had this problem as well, and I think it is because the system was upgraded from an older version where the files were in a different location. Firefox is probably picking up old versions of some files.

I ran a command prompt in “\Program Files\Mozilla Firefox” and did “dir inspector*.* /s”. This found a bunch of files beginning with “inspector” in subdirectories chrome, components, defaults\prefs extensions\inspector@mozilla.org, and res. On a system where the DOM inspector was working properly the dir command only found files in extensions\inspector@mozilla.org.

Deleting all of the files matching “inspector*.*” except those under extensions should fix the problem. (I’m not absolutely certain it does because what I actually did was to delete all files beginning with inspector and then reinstalled Firefox on top of the existing installation).

By: David

David — Fri, 17 Nov 2006 13:10:25 +0000

After noticing that DOM Inspector correctly worked on another machine, I uninstalled Firefox and all other variants of Mozilla and reinstalled Firefox 2. That fixed the problem.

By: David

David — Fri, 17 Nov 2006 12:52:06 +0000

I’m glad I found this page. I thought that some other extension had been screwing up DOM Inspector.

By: hank

hank — Wed, 15 Nov 2006 09:53:53 +0000

Thanks for stopping in everyone. I just updated the post with a workaround that works for me, I hope it helps you guys. In the end though, the FF guys need to come up with something to fix it properly.

By: Peter

Peter — Fri, 10 Nov 2006 04:07:55 +0000

Ditto here. I kind of think it started when I upgraded from 1.5 to beta 2 in September…

By: Simon

Simon — Tue, 07 Nov 2006 15:52:23 +0000

Just adding my name to the list… Yup, its a Firefox 2 issue, alright. And a damn annoying one at that!..

By: Pedro

Pedro — Tue, 07 Nov 2006 09:52:49 +0000

I get that problem too – I just did a google search to see if there were any fixes out there and I came across your page… No luck in finding a solution yet…

By: Kirk

Kirk — Sun, 05 Nov 2006 00:56:57 +0000

I get to say “Me too!”. Very frustrating, as the CSS style rules is my most used part of the DOM inspector. I’m glad I found your page so I knew I wasn’t alone.

By: Rory

Rory — Fri, 03 Nov 2006 13:57:09 +0000

Yeah totally, I get the exact same problem now, it also effects the Style tab within the Inspector panel, within the now famous Firebug extension… that too is blank :’(