Re: Connecting and Disconnecting events for IHTMLWindow2
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Thu, 18 Aug 2005 13:21:13 -0400
Zach <divisortheory@xxxxxxxxx> wrote:
> Say I have page A with frames B and C. Order of events might be
> something like this:
>
> BeforeNavigate2(A)
> BeforeNavigate2(B)
> BeforeNavigate2(C)
>
> NavigateComplete2(A)
> NavigateComplete2(C)
> NavigateComplete2(B)
Impossible. To kick off navigation for B and C, A needs to know that
they exist. For that, it needs to actually see the HTML code that
contains the appropriate <frame> or <iframe> tags. But the first byte of
content is only seen after NavigateComplete2 event. Thus,
BeforeNavigate2(B) and BeforeNavigate2(C) can only appear after
NavigateComplete2(A).
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
.
- Follow-Ups:
- References:
- Connecting and Disconnecting events for IHTMLWindow2
- From: Zach
- Re: Connecting and Disconnecting events for IHTMLWindow2
- From: Igor Tandetnik
- Re: Connecting and Disconnecting events for IHTMLWindow2
- From: Zach
- Re: Connecting and Disconnecting events for IHTMLWindow2
- From: Igor Tandetnik
- Re: Connecting and Disconnecting events for IHTMLWindow2
- From: Zach
- Re: Connecting and Disconnecting events for IHTMLWindow2
- From: Igor Tandetnik
- Re: Connecting and Disconnecting events for IHTMLWindow2
- From: Zach
- Connecting and Disconnecting events for IHTMLWindow2
- Prev by Date: Re: Connecting and Disconnecting events for IHTMLWindow2
- Next by Date: Re: Connecting and Disconnecting events for IHTMLWindow2
- Previous by thread: Re: Connecting and Disconnecting events for IHTMLWindow2
- Next by thread: Re: Connecting and Disconnecting events for IHTMLWindow2
- Index(es):