client side script with RegisterStartupScript issue

[bruce barker]

no, you can not control the order the blocks are rendered. you can concat
the scripts and register them once. also
if you are doing code like:

<script> window.open([url]http://myurl);[/url] </script>

to open the window on postback, you should reengineer unless its an entranet
site. popup ad blockers, an i hope IE soon (Netscape, Opera, etc already
do), block the execution of this code. window.open should only be legal from
a client click event.

-- bruce (sqlwork.com)



..




"Dave Stienessen" <daves@xata.com> wrote in message
news:eM44KB5VDHA.384@TK2MSFTNGP12.phx.gbl...

> I have some web pages that will issue script to spawn a url in another
> window after the page posts back and sets focus to the new window - the

same

> pages contain web user controls that put in script in the page that sets
> focus to a control on the form -
>
> The problem I run into is the script that launches the new browser gets

put

> into the html 1st and the script for setting focus in the use control gets
> run 2nd - the behavior because of this is that my new window gets

launched,

> gets focus, then the script that sets focus in the old window runs and
> returns focus to the original window (apparently setting focus to a

control

> grabs focus for the entire window)
>
> It seems like a good enhancement to RegisterStartupScript would be a
> relative order of the script so I could force my "new Window" script to

run

> last - Is there any way that I can control the ordering of how ASP.NET
> renders these?
>
> TIA
> Dave
>
>

[Dave Stienessen]

I was afraid of that... Thanks for the input - our script code does take
into account popup blockers - if the window fails to open in script, it
redirects to the page within the same window -
Thanks again...

"bruce barker" <nospam_brubar@safeco.com> wrote in message
news:ufo4U55VDHA.1896@TK2MSFTNGP12.phx.gbl...

> no, you can not control the order the blocks are rendered. you can concat
> the scripts and register them once. also
> if you are doing code like:
>
> <script> window.open([url]http://myurl);[/url] </script>
>
> to open the window on postback, you should reengineer unless its an

entranet

> site. popup ad blockers, an i hope IE soon (Netscape, Opera, etc already
> do), block the execution of this code. window.open should only be legal

from

> a client click event.
>
> -- bruce (sqlwork.com)
>
>
>
> .
>
>
>
>
> "Dave Stienessen" <daves@xata.com> wrote in message
> news:eM44KB5VDHA.384@TK2MSFTNGP12.phx.gbl...

> > I have some web pages that will issue script to spawn a url in another
> > window after the page posts back and sets focus to the new window - the

> same

> > pages contain web user controls that put in script in the page that sets
> > focus to a control on the form -
> >
> > The problem I run into is the script that launches the new browser gets

> put

> > into the html 1st and the script for setting focus in the use control

gets

> > run 2nd - the behavior because of this is that my new window gets

> launched,

> > gets focus, then the script that sets focus in the old window runs and
> > returns focus to the original window (apparently setting focus to a

> control

> > grabs focus for the entire window)
> >
> > It seems like a good enhancement to RegisterStartupScript would be a
> > relative order of the script so I could force my "new Window" script to

> run

> > last - Is there any way that I can control the ordering of how ASP.NET
> > renders these?
> >
> > TIA
> > Dave
> >
> >

>
>