Closed Bug 439638 Opened 18 years ago Closed 18 years ago

DOM Inspector broken - shows no DOM Nodes and other problems

Categories

(Other Applications :: DOM Inspector, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: philip.harvey, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9) Gecko/2008052906 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9) Gecko/2008052906 Firefox/3.0 I just installed DOM Inspector 2.0.0 (https://addons.mozilla.org/en-US/firefox/addon/6622). Unfortunately it looks quite broken. The buttons to inspect the pointed-to element, and fine a node with particular id do nothing. Also, the "DOM Nodes" pane is always blank (although it does successfully show Stylesheets, Javascript objects etc). I did previously have other versions of Firefox installed - not sure if this is relevant. Reproducible: Always Steps to Reproduce: 1. Download firefox 2. Download DOM Inspector 2.0.0 3. Open DOM Inspector. Actual Results: Observe the lack of DOM Nodes. Expected Results: DOM Nodes showing.
Component: Extension Compatibility → DOM Inspector
Product: Firefox → Other Applications
QA Contact: extension.compatibility → dom-inspector
This works for me - do you have any other add-ons installed?
(In reply to comment #1) > This works for me - do you have any other add-ons installed? > Hi, I've got the following installed but I've disabled them all in an attempt to fix the problem: adblock plus, firebug, greasemonkey, ie tab, tamper data, yslow. I'm pretty sure DOM Inspector has never worked for me, even when I was running Firefox 2.x. Is there an internal config file I can check or clean up?
Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9) Gecko/2008052906 Firefox/3.0 XP home SP2 add-ons : Cacheviewer 0.4.7.1, DictionnarySearch 3.0.0, DownloadHelper 3.0.4, FireBug 1.2.0b3, FireFTP 0.99.1, WizzRSS 3.0.0.0 Hi, I've exactly the same prob as Philip Harvey, namely the DOM nodes pane is blank PLUS: 1) when I return back to "DOM nodes" from another pane (ie scripts, styelsheets), the DOM nodes pane label is not refreshed 2) in "accessible trees" pane when pointer passes over any row, the names in column "node names" vanish 3) sometimes I must go to others panes before "stylesheets" pane could display successfully. -------- when previuosly using built-in DOMI with FF2 everything was working correctly
This seems to be due to old left-over files in the installation directory. I got rid of the problem as follows 1. uninstalled the DOM Inspector 2. checked Program Files\Mozilla Firefox for all files older than 2008-01-01 3. removed anything that wasn't obviously related to an older plugin Complete list of what I removed: 2003-01-14 18:10 660 nsI4xScriptablePluginVirtools.xpt 2004-11-07 13:57 46 installed-extensions-processed.txt 2004-12-01 17:50 139.264 npvirtools.dll 2004-12-02 08:40 1.107 Extensions.rdf 2005-09-15 18:26 4.832 inspector-cmdline.js 2005-09-15 18:26 44.153 inspector.dll 2005-09-15 18:26 562.372 inspector.jar 2005-09-15 18:26 2.135 inspector.js 2005-09-15 18:26 2.980 inspector.xpt 2005-09-15 18:26 1.779 platform-forms.css 2005-09-15 18:26 390 search-registry.rdf 2005-09-15 18:26 3.411 viewer-registry.rdf 2005-10-23 23:48 0 initdebug.nfo 2005-12-02 00:20 24 components.ini 2005-12-02 00:20 24 defaults.ini 2006-08-07 04:51 150.912 fullsoft.dll 2006-09-16 23:34 8.822 qfaservices.dll 2007-04-02 16:42 0 .autoreg 2007-04-24 11:36 1.452.416 npLegitCheckPlugin.dll 2007-05-31 08:35 13.058 removed-files 2008-07-05 00:26 <DIR> inspector Some of these are obviously obsolete plugins that should be unrelated to the problem but I listed everything I removed for completeness.
WORKSFORME per comment 4
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
(In reply to comment #4) works for me to *BUT* there is still a problem in pane "accessible tree" : when flying over a row, the name of a node in column "node name" is still being cleared
You need to log in before you can comment on or make changes to this bug.