Re: WebBrowser Control and window.open
- From: "Rene Pilon" <rspilon@xxxxxxxxxxx>
- Date: Sat, 31 Jan 2009 11:33:46 -0500
It's probably due to a cross domain security issue.
Does this apply to what you are doing:
http://codingthriller.blogspot.com/2008/01/pain-of-cross-domain.html
Regards,
Rene Pilon
"Carlo Marchesoni" <CarloMarchesoni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:223EEC0D-77F8-4478-B7B1-0C4AFD73BAC2@xxxxxxxxxxxxxxxx
I would like to embed an IE browser into a Windows app (WPF or FormsApp
doesn't matter).
It basically works, but whenever one of the pages I point to (I am using a
aspx app with FormsAuthentication) have a 'window.open' javascript
command,
the new Window opens with the Login page. Looks like the session state is
not
treated correctly when using the webbrowser control.
Is this something that can be changed with a setting somewhere ?
thank you for your help
.
- References:
- WebBrowser Control and window.open
- From: Carlo Marchesoni
- WebBrowser Control and window.open
- Prev by Date: Transparent start menu
- Next by Date: Re: Scrolling Dialog
- Previous by thread: WebBrowser Control and window.open
- Next by thread: Re: how to create a process with hidden state?
- Index(es):