Closed Bug 20332 Opened 25 years ago Closed 23 years ago

DOM viewer never loads under M11 on NT

Categories

(SeaMonkey :: General, defect, P3)

x86
Windows NT

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: kennedyh, Assigned: alecf)

References

()

Details

using M11 (Build ID: 1999111520) on WinNT4 sp5, trying to open the DOM Viewer

(Debug->DOM Viewer)

never opens the DOM Viewer.
Mozilla just sits there with the progress bar spinning.
Its not burning much CPU (per the task manager) and does not
refresh the window contents (dragging another window infront of it
leaves "tracers" in the main browser window).

this is due to it looking for a non-existant file (?)
it was looking for

m11/bin/chrome/domviewer/content/default/DOMDataSourceViewer.xul
when the file _actually_ lives at
m11/bin/chrome/domviewer/chrome/content/default/DOMDataSourceViewer.xul
on NT.
hmm.. this may be related, but after actually loading the DOM viewer by hand,
the "Refresh" button in the left frame dumps the following error:


JavaScript Error: TypeError: domds has no properties
URL:
file:///C|TEMP/m11/bin/chrome/domviewer/chrome/content/default/DOMDataSourceViewer.js
LineNo: 51
that error is due to DOM security I believe...
Status: NEW → ASSIGNED
Target Milestone: M13
Target Milestone: M13 → M20
Moving DOM viewer bugs to future. I do not expect to get to these bugs any time
soon, so feel free to work on them.
Target Milestone: M20 → Future
This bug is on the path to wontfix... see bug 92892, Remove the DOM Viewer from 
the build (and replace it with the DOM Inspector?).
wontfix, as the document inspector is the replacement to DOM viewer
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Obsolete DOM Viewer bugs -> Browser-General; DOM Viewer component is going away.
Component: DOM Viewer → Browser-General
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.