DOM_CLASSINFO_DOCUMENT_MAP_ENTRIES doesn't have nsIDOMDocument

RESOLVED WONTFIX

Status

()

Core
DOM
RESOLVED WONTFIX
7 years ago
5 years ago

People

(Reporter: Ms2ger, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
As seen in bug 655517.
Want to fix?  ;)
(Reporter)

Comment 2

7 years ago
Created attachment 532460 [details] [diff] [review]
Patch v1

I can, but that doesn't mean I know what effect it will have.
Assignee: nobody → Ms2ger
Status: NEW → ASSIGNED
Attachment #532460 - Flags: review?(bzbarsky)
Comment on attachment 532460 [details] [diff] [review]
Patch v1

Hmm.  Well, neither do I.  The patch as given will cause duplicate DOM_CLASSINFO_MAP_ENTRY(nsIDOMDocument) for a bunch of document classes and will cause others to contain both DOM_CLASSINFO_MAP_ENTRY(nsIDOMDocument) _and_ DOM_CLASSINFO_MAP_ENTRY(nsIDOMHTMLDocument).  I presume this last is why the entry is not in DOM_CLASSINFO_DOCUMENT_MAP_ENTRIES to start with, but I'm not sure whether the duplication is a problem.
Attachment #532460 - Flags: review?(bzbarsky) → review?(peterv)
(In reply to comment #3)
> The patch as given will cause duplicate
> DOM_CLASSINFO_MAP_ENTRY(nsIDOMDocument) for a bunch of document classes

Please don't do that.

> will cause others to contain both DOM_CLASSINFO_MAP_ENTRY(nsIDOMDocument)
> _and_ DOM_CLASSINFO_MAP_ENTRY(nsIDOMHTMLDocument).

Harmless but unneeded, code that uses this walks the interface chain of every interface in the array anyway, so nsIDOMDocument is hit as part of nsIDOMHTMLDocument

What are we trying to fix exactly?
Comment on attachment 532460 [details] [diff] [review]
Patch v1

You should at least remove nsIDOMDocument from any class that uses DOM_CLASSINFO_DOCUMENT_MAP_ENTRIES.
Attachment #532460 - Flags: review?(peterv) → review-
(Reporter)

Comment 6

7 years ago
What I'm trying to fix is Olli's comment in bug 655517. If nothing is wrong here, please close this bug.

Comment 7

7 years ago
I was complaining about the inconsistency in nsDOMClassInfo. In some cases
nsIDOMDocument is there, some cases not.
Where "there"?
(Reporter)

Comment 9

5 years ago
Let's kill DOMCI instead.
Assignee: Ms2ger → nobody
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.