ScriptManager Navigate event clarification.

[msch.prv@gmail.com]

I am using ASP.NET 3.5 Extension and have some questions about the
ScriptManager navigation event.

1. What exactly causes the ScriptManager navigation event to fire? Is
it a change of the url address (caused by adding a history point for
example), clicking on the browser's return button, or something else?
2. Should the navigation event fire only when one of the above events
takes place or always whenever a post-back is issued? 3. Finally, is
there a way to differentiate among the trigger sources, for instance
between the current or an external page? (IsCrossPagePos tBack does not
seem to work in my case). TIA for any hints.

[bruce barker]

Re: ScriptManager Navigate event clarification.

history points are created by creating bookmarks navigatng to them to
add the bookmark with a decorated url to the browser history (pretty
standard approach). when the user navigates the history, if the url is
decorated (thus identifying the navigation a history checkpoint) then
the navigate event is fired.

-- bruce (sqlwork.com)


msch.prv@gmail. com wrote:

I am using ASP.NET 3.5 Extension and have some questions about the
ScriptManager navigation event.
>
1. What exactly causes the ScriptManager navigation event to fire? Is
it a change of the url address (caused by adding a history point for
example), clicking on the browser's return button, or something else?
2. Should the navigation event fire only when one of the above events
takes place or always whenever a post-back is issued? 3. Finally, is
there a way to differentiate among the trigger sources, for instance
between the current or an external page? (IsCrossPagePos tBack does not
seem to work in my case). TIA for any hints.