155003 - DOM Inspector doesn't show any nodes

Status: VERIFIED INVALID

(Other Applications :: DOM Inspector, defect)

Description

[Devin Bayer]

When the DOM Inspector is installed it doesn't show any nodes in the "DOM Nodes"
view.  Stylesheets and JS Objects are shown.  This happens both as a sidebar and
as a seperate window.  The list is empty; but white, not grayed out.  This
happens on any page I've visited.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020615 Debian/1.0.0-3

I have tried installing the DOM Inspector both from the RC3 XPI at
http://grayrest.com/moz/evangelism/tutorials/dominspectortutorial.shtml and the
Debian Package.

After installing the XPI (the Debian Package was already installed) I got this
error message on startup once:
**************************************************
nsNativeComponentLoader:
SelfRegisterDll(/usr/lib/mozilla/components/libinspector.so) Load FAILED with
error: libmozz.so: cannot open shared object file: No such file or directory
**************************************************

There is no libmozz.so in any package.

Comment 1

[Andrew Schultz]

I think what you're seeing might be a result of using the Mozilla-built DOM
Inspector with the Debian-built Mozilla.  Could you try using Debian's DOM
Inspector, or install the full Mozilla build?

http://download.mozilla.org/pub/mozilla/releases/mozilla1.0/mozilla-i686-pc-linux-gnu-1.0-sea.tar.gz

Comment 2

[timeless]

not our bug.  please complain to the debian maintainers for not packaging a 
libmozz.so (it's mozilla's libz.so, a symlink to your distro's libz.so will 
work, and you should be able to suggest that if they insist on building mozilla 
w/ system zlib, that they *MUST* package that symlink).

Please verify that the symlink works, and change the url here to a bug report 
which you will file in DBTS

Comment 3

[Tim]

Yes, see package mozilla-dom-inspector (or -snapshot) for this functionality.

If you insist on being able to use Mozilla DOM Inspector XPIs (or
to--potentially--be able to do this with other Mozilla-based XPIs), do the
following (as root) *before* installing the XPI:

#ln -s /usr/lib/libz.so.1 /usr/lib/mozilla/libmozz.so

libz.so from the -dev package works, and I haven't tried libz.so.2 (YMMV).
After that change, by my testing, the Mozilla-packaged DOM inspector works.

Right now, there are no specifications as to what XPIs may and may not expect
(or what conditions mozilla packagers must meet to accept Mozilla-ready XPIs). 
For this reason, you should not (in my opinion) expect Mozilla-ready XPIs to
work with Mozilla packages from third-party distributors.

If there is a bug here, I would think it is that XPIs can overwrite files
installed by other XPIs.  If that is not a bug or if it should be filed
elsewhere (and isn't already), I recommend resolving this bug invalid.

Also, to the reporter: it would be helpful to mention what you consider expected
behavior to be (refuse to install the XPI?).

Comment 4

[timeless]

um, the xpi's need to be able to overwrite, since you need to be able to use an 
xpi to upgrade a package/component. however this isn't what happened, the xpi 
installed a new component which expected a *core* component of mozilla to be 
present, and that component didn't work .. no harm done.

I'd also like to take issue with this statement:
> There is no libmozz.so in any package.
a quick google search shows that there is a libmozz.so in *many* packages and 
that each package it's in is a *core* package of mozilla.

Comment 5

[Devin Bayer]

Andrew and Tim: I did try the Debian DOM Inspector first.
Tim: expected behavior: the DOM inspector should work correctly.
timeless:
I meant "There is no libmozz.so in any _Debian_ package."  Sorry for the
confusion.  Also, I have changed the URL field to reflect a bug report I filed
with Debian.

Comment 6

[timeless]

vrfy bug is moved to DBTS.