Closed
Bug 56881
Opened 24 years ago
Closed 24 years ago
domviewer only displaying unknown:unknown
Categories
(SeaMonkey :: General, defect, P5)
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: axel, Assigned: hewitt)
Details
Attachments
(1 file)
1.93 KB,
text/plain
|
Details |
There are quite a few bugs on domviewer, but most have a ancient history, and started off as something different. So I create a new specific one. After jag change the xul to get rid of a rdf: namespace, the domviewer came back to something close to life. But it only shows "unknown" for name and value. As far as gdb made me go, this is due to the QI to nsIDOMViewerElement in http://lxr.mozilla.org/seamonkey/source/rdf/tests/domds/nsRDFDOMDataSource.cpp#735 failing. Then the resources loose their dom nodes, and the thing goes down. At least that's what I think. Tested on CVS from Oct. 16. Axel
Comment 1•24 years ago
|
||
hewitt is reviving domviewer for his property inspector. Have jag's changes been checked in?
Reporter | ||
Comment 2•24 years ago
|
||
jag's stuff is checked in, http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=mozilla/rdf/tests/domds/resources&command=DIFF_FRAMESET&file=DOMDataSourceViewer.xul&rev1=1.18&rev2=1.19&root=/cvsroot Axel
Assignee | ||
Comment 3•24 years ago
|
||
The reason it displays unknown unknown is that the wrong resource factory id is being used at: http://lxr.mozilla.org/seamonkey/source/rdf/tests/domds/nsRDFDOMDataSource.cpp#7 25 simply change "object://" to "dom://" and voila it works.
Assignee | ||
Comment 4•24 years ago
|
||
I'm attaching a file with two patches that fix the DOM Viewer 100% (in addition to jag's changes). The other change is just adding a class="treecell-indent" to the xul.
Assignee | ||
Comment 5•24 years ago
|
||
Reporter | ||
Comment 6•24 years ago
|
||
So this was rather easy. Just noting the following: I don't know what to expect, but it looks like the Name's are all empty(?). If I selected dom, and then select frames, I get a segfault. Too late to start debuggin tonight, I might come up with something more useful later. Anybody to verify this? Anyway, this is a good step forward. Axel
Comment 8•24 years ago
|
||
name shouldn't be blank, that should be the the "nodeName" attribute of the node.
Reporter | ||
Comment 9•24 years ago
|
||
r=axel@pike.org, I don't see the problems with the missing display values anymore. May have been my fault, or something changed elsewhere fixing this. Axel
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•24 years ago
|
Priority: P3 → P5
Assignee | ||
Comment 10•24 years ago
|
||
I'm not planning on working on the old DOM viewer anymore. A long time ago I started a new project called document inspector which extends DOM Viewer in many new directions. I'm still trying to get this checked into the tree. Marking WONTFIX
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
verified. Joe has checked his document inspector into the tree (I believe you have to build with special flags, but it's there.)
Status: RESOLVED → VERIFIED
Comment 12•22 years ago
|
||
Obsolete DOM Viewer bugs -> Browser-General; DOM Viewer component is going away.
Component: DOM Viewer → Browser-General
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•