Re: Windowless WebBrowser control?

From: Gambini (buiv1_at_yahoo.com)
Date: 06/29/04 

Date: 29 Jun 2004 06:55:40 -0700

Charles,
  
  I've noticed certain attributes like the BODY bgColor don't hold the
"correct" value--for instance when the bgColor is changed with a
style*** or an inline style. Also, the WebBrowser can do XML
transformations. Those are some things off the top of my head that
make the WebBrowser's DOM different from just the MSHTML parsing's
DOM.

"Charles Law" <blank@nowhere.com> wrote in message news:<ek6UmWWXEHA.1684@tk2msftngp13.phx.gbl>...
> > Note that lightweight MSHTML parsing doesn't return quite
> > the complete DOM as when parsed with a WebBrowser control object.
>
> What exactly is the difference that you see?
>
> There is no reason why mshtml should not return the DOM in the same way as
> the WebBrowser control. The browser control uses mshtml for the DOM and
> ShDocVw for rendering.
>
> Charles
>
>
> "Gambini" <buiv1@yahoo.com> wrote in message
> news:43ed48c4.0406280803.33b51d6a@posting.google.com...
> > "Igor Tandetnik" <itandetnik@mvps.org> wrote in message
> news:<eahSc6tWEHA.212@TK2MSFTNGP12.phx.gbl>...
> > > "Gambini" <buiv1@yahoo.com> wrote in message
> > > news:43ed48c4.0406250825.d1bf0fa@posting.google.com
> > > > "Igor Tandetnik" <itandetnik@mvps.org> wrote in message
> > > > news:<#LgbxwgWEHA.3016@tk2msftngp13.phx.gbl>...
> > > >> "Gambini" <buiv1@yahoo.com> wrote in message
> > > >> news:43ed48c4.0406240832.2c73f1d6@posting.google.com
> > > >>> Is it possible to use a WebBrowser control without creating a window
> > > >>> to host it?
> > > >>
> > > >> No.
> > > >
> > > > Besides hosting the WebBrowser object in an invisible window, what
> > > > are the next best things I can do to limit code, system resources,
> > > > etc. (such as not painting the rendered webpage) if I do not require
> > > > the WebBrowser UI?
> > >
> > > What's wrong with the hidden window again?
> >
> > Just that it's not needed for the MSHTML parsing done that I
> > require. Note that lightweight MSHTML parsing doesn't return quite
> > the complete DOM as when parsed with a WebBrowser control object.