9974 - nsIAppShellService should only deal with IDLized interfaces

Status: VERIFIED INVALID

(Core :: XUL, defect, P1)

Description

[travis]

(This bug imported from BugSplat, Netscape's internal bugsystem.  It
was known there as bug #358213
http://scopus.netscape.com/bugsplat/show_bug.cgi?id=358213
Imported into Bugzilla on 07/15/99 22:18)

There are currently methods found inside nsIAppShellService that deal with
*private* interfaces.  For example CreateTopLevelWindow() returns a
nsIWebShellWindow for the created window.  nsIWebShellWindow is considered a
private interface.  Since interfaces like this are considered private, IDL files
should not be created for them.  Without IDL files for each interface that
nsIAppShellService passes around, it can not properly be marshaled with the
XP-COM Proxy code.

nsIAppShellService should be changed to deal with only "public" interfaces that
have IDL files describing their v-table layout.

Comment 1

[mgong]

nsIAppShellService should be changed to deal with only "public" interfaces that
have IDL files describing their v-table layout.

Comment 2

[Dan M]

The decision to make nsAppShellService a public, IDLized interface has since been revisited and
recognized as an error.  The solution currently in favor is to make useable the window creation code
in nsIDOMWindow, and allow the window creation code in nsAppShellService to remain private.
I believe that obviates any need to subject it to proxying, so this becomes a moot topic.

Comment 3

[Jay Patel [:jay]]

verified invalid