Forgot one more place i use nsPIDOMWindow  is to get nsIFocusController

"C.N.Medappa" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Thanks for the info, may be i should not be using it.
>
> Presently i am using :-
> 1) nsIDOMWindowInternal to get nsPIDOMWindow ,
> 2) nsPIDOMWindow is used to get nsIDocShell and nsIChromeEventHandler
>
> Is there any other way i can reach nsIChromeEventHandler and nsIDocShell
> without nsPIDOMWindow
>
> Thanks
> +Medappa
>
>
> "Boris Zbarsky" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > C.N.Medappa wrote:
> > > 1) Why are some interfaces De-COMized ?
> >
> > Performance improvement and footprint reduction, as well as code
> readability.
> >
> > > 2) What are the Intefaces that will be De-COMized in future ?
> >
> > Pretty much anything that's a layout/content/widget (and maybe gfx)
header
> and
> > is a .h instead of .idl is fair game.  The actual criterion that's used
is
> that
> > if it's basically a private layout/content header (some of these
> "interfaces"
> > shouldn't even be named nsIwhatever), it should be deCOMtaminated.
> >
> > > Since i am using non-geko-sdk interfaces i need to modify my source
for
> each
> > > release of Mozilla.
> >
> > Why do you need to use non-sdk interfaces?  Especially ones subject to
> > deCOMtamination?  We should talk; perhaps we need to expose the
> functionality
> > you need in some other way.
> >
> > -Boris
>
>


_______________________________________________
mozilla-embedding mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-embedding

Reply via email to