In fact, that documentation needs to be updated. The nsIWebBrowserPrint will soon be a "requestor" interface and not a implemented interface.

Rod


Judson Valeski wrote:
[EMAIL PROTECTED]"> cc'ing the newsgroup (I hope you don't mind).

IIRC, we haven't resolved this yet.  Because it is indeed object, rather than interface specific, it falls into the implementation detail :-/ (reason # 43 why GI is a gaping hole). I guess for now, it's pure documentation (not even in a header/idl file).? Look what Rick did in his doc cut . He outlined specific implementations, and listed their "Requestor Interfaces." This implies that we need to freeze implementations which is something we're trying to avoid :-/

I'm not sure what the best way to handle this is; any ideas?

Jud

Rod Spears wrote:
Where is the documentation for what interfaces are supported by GetInterface for a particular object?

For example, if I am a consumer of our embedding APIs is there an easy, logical place to go to to find out what interfaces are available via QI and what are available via GetInterface?

Rod




Reply via email to