92892 - Remove the DOM Viewer from the build and bugzilla

Status: VERIFIED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[rbs]

Apparently, the DOM Viewer isn't maintained anymore. Instead, more effort
seems to be going into the DOM Inspector which does what the DOM Viewer used
to do. So the DOM Viewer could be removed (footpring) and perhpas...
a transition could be made to the DOM Inspector (in the build system & bugzilla
component).

Below is the n.p.m.dom post that prompted me to enter this bug in bugzilla:

     Subject: Re: DOM Viewer
        Date: Mon, 30 Jul 2001 13:43:13 -0700
        From: Heikki Toivonen <[e-mail]>
  Newsgroups: netscape.public.mozilla.dom

Heikki Toivonen wrote:
> 
> Forget DOM Viewer. Inspector does everything DOM Viewer did, and then
> some. It is not built by default, but you can do it yourself. It is in
> mozilla/extensions/inspector
> 
> Frank Burleigh wrote:
> 
> > Whatever happened to the DOM Viewer?  I mention it because I feel
> > certain I saw recently something in bugzilla something about bringing
> > the DOM Viewer back to life.  Yet Debug/DOM Viewer does nothing for me
> > except sometimes put something in the URL.  I'm on win2k using recent
> > builds.  Thanks.
> 
> --
>    Heikki Toivonen

Comment 1

[Jesse Ruderman]

See also bug 20332, dom viewer hasn't worked on Windows since M11.

Comment 2

[Asa Dotzler [:asa]]

There are a lot of us that would love to see the DOM Inspector turned on by
default in the nightly and next (0.9.5) Milestone build. 

Comment 3

[Asa Dotzler [:asa]]

updating this bug to just cover the removal of the DOM viewer. Enabling the
Document Inspector is now bug 102574. Hope that's cool with everyone. 

Comment 4

[rbs]

Seems that the DOM Viewer is now gone from the trunk, in which case it just
remains to remove the bugzilla's DOM Viewer component.

Comment 5

[Bernd]

the menu entry in the debug menu is still available

Comment 6

[Bradley Baetz (:bbaetz)]

Attachment: remove dom viewer from debug menu

Comment 7

[Bradley Baetz (:bbaetz)]

Quite a few people on #bugweek were confused about this, and wonce dom inspecter
is on by default, it will just get more confusing.

I'll get this reviewed and checked in, then move this bug to get the component
removed from bugzilla.

Comment 8

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 55484 [details] [diff] [review]
remove dom viewer from debug menu

r=bzbarsky

Comment 9

[Darin Fisher]

Comment on attachment 55484 [details] [diff] [review]
remove dom viewer from debug menu

sr=darin

Comment 10

[Bradley Baetz (:bbaetz)]

OK, checked in.

-> m.o/component changes to get this component removed/obsoleted. I suppose all
the open bugs have to get resolved WONTFIX, since I don't think we can obsolete
components, only products.

Comment 11

[Diego Biurrun]

Is this fixed now?  The patch seems to have been checked in, the DOM inspector
is enabled in all current builds..

Comment 12

[Asa Dotzler [:asa]]

The DOM Viewer is still a component. I need to retire it but that means moving
bugs out of the component. 

Comment 13

[Asa Dotzler [:asa]]

this bug as originally reported is actually fixed. I'm not sure what to do with
the bugs in the Dom Viewer component and I can't remove the component without
moving those bugs. 

Comment 14

[rbs]

Since bugs targeted against a dead program don't make sense, perhaps you can 
just go ahead and do a mass delete of those bugs, thereby clearing the way for 
deleting its bugzilla component.

Comment 15

[timeless]

Deleting bugs is bad.

Asa, I see a few options
1. create mozilla.org:graveyard and move all orphanned bugs there [a bit of data is lost from basic queries, but everything is preserved in history]
2. move these bugs to browser-general

Comment 16

[Hixie (not reading bugmail)]

->me

Comment 17

[Hixie (not reading bugmail)]

done.

Comment 18

[timeless]

dom viewer bugs were moved to browser general

vrfy fixed