win32: internet explorer automation problem

[John J Lee]

[sorry to send this separately from my direct email reply, but the headers
implied that Micha's reply wasn't sent to the newsgroup]

On Fri, 9 Jan 2004, [iso-8859-2] Micha³ ¯yliñski wrote:
[...]
> I don't think this could work - my piece of code is assumed to be completely
> separated from the HTML itself.

I don't know what you mean by that.

> It just 'watches' the MSIE behaviour and
> simulates the user work.

And...?


> AFAIK opening popup creates another MSIE instance,
> so I simply loose the context.

That should just be an implementation detail, shouldn't it?


> It'd be perfect if external window will be
> treated using IHTMLDocument object model,

It is.  Or at least, I'd be amazed if it weren't.  How else would people
use popups from JavaScript via the usual window interface?


> but window object works according
> to this excerpt from MSDN like this:
>
> 'Typically, the browser creates one window object when it opens an HTML
> document. However, if a document defines one or more frames (that is,
> contains one or more frame or iframe tags), the browser creates one window
> object for the original document and one additional window object for each
> frame'

And...?

There is presumably some way of doing this from JavaScript (right?): so do
the same using the interfaces exposed via COM.


> So there is no easy way of doing it like
> Document.NewWindow.documentelement.outerHTML. There is some ppDisp parameter

What's NewWindow, here?


John