101804 - DOM Other component is obsolete

Status: VERIFIED WONTFIX

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

Description

[gerardok]

The "DOM Other" component was originally set up in Bugzilla to hold bugs that do 
not fit into any other existing DOM Component --and to hold all bugs from the 
old DOM Level 1 and Level 2 components.

Right now, Bugzilla has DOM components for each specification described in DOM 1  
and DOM 2, and DOM 3 Load and Save, so I'd like to get the "DOM Other" component 
deprecated. It will prevent many undetermined bugs (not even DOM) from being 
transferred there for further investigation, and we can have additional DOM 
components created if needed.

The component description for DOM Other reads:
For bugs in DOM support which do not fit into any other DOM Component

It should be updated to:
This component is deprecated. Please use the DOM component related to the 
specific DOM feature where your bug is located.

jst, joki, vidur please let me know what do you think.

Comment 1

[Asa Dotzler [:asa]]

Unfortunately, people do not read Component descriptions when reporting bugs so
changing the description won't help. If we want to stop bugs from landing in
that Component we should remove the Component. To do that we need to move all
the bugs out of the Component. 

Additionally, Most reporters do not know which of the DOM components to file DOM
bugs. This included people at Netscape in qa and devel. Perhaps we should rename
DOM Other to DOM or DOM General or something like that. Then people who didn't
know would have a clear bucket to file DOM bugs rather than misfile on one of
the real Components. Someone who knows the DOM Components well could QA that
Component and do the proper reassigning. 

Comment 2

[Hixie (not reading bugmail)]

DOM Other was not created to hold bugs from the old DOM Level 1 and DOM Level 2 
components (I know, I was the one who asked for their creation).

This component exists to hold bugs in areas of DOM that do not yet have a 
component, and may never have one, e.g. DOM XPath, DOM XPointer, or DOM SVG, 
which currently either have no spec or do not (yet) rate their own component.

DOM Other should not be "deprecated", since it is still very much useful.
I agree with Asa that the DOM Other QA Contact should be taking a few seconds
a day to triage the bugs, though.

Comment 3

[Fabian Guisset]

If noone else wants it I'm ok to become the default QA contact for DOM Other
since I know pretty well where DOM bugs have to go, and don't mind the extra
mail. I agree that DOM other should be kept, it's useful.

Comment 4

[Asa Dotzler [:asa]]

Sounds like we have disagreement over what this component is for. Do we need to
make any changes here still?

Comment 5

[Asa Dotzler [:asa]]

wontfix.

Comment 6

[timeless]

vrfy wontfix

if someone wants to file a bug to change the default QA contact to fabian, feel 
free...