Application getting closed if javascript sends window.close() to cefsharp browser - cefsharp

I am using cefsharp.winforms Chromium browser and I am opening a video inside the browser. There is a close button in the video. On clicking the close button the whole application is getting closed. Seems like from javascript window.close() is getting called and app is getting closed.
I have tried setting disable-javascript-close-windows to 1 for cef flags but still the application is getting closed.
I have also tried handling LifeSpanHandler DoClose event from where I am returning true but that also not working.( This doesn't close the app but goodbye.html is also not appearing which I am getting as a callback)
"I expect the GoodBye html page to get open on clicking the close button. I am getting the goodbye.html callback but before that application is getting closed."

Related

Cross domain communication between iframe and content window without refreshing the iframe window

i am currently working on a project where i have to use iframe . how do I achieve cross domain communication (i.e. between content window and iframe) ?
i am using asp.net. Also each time i try to send a message using parent.postMessage() the iframe seems to be refreshing and i am able to see message for fraction of second. How to stop it from refreshing?

Hyperlink or Browser BACK button

Is there any way to find out what caused the current GET request in ASP.NET (MVC 4 in perticular) ? I need to write server-side code that takes some special actions if the current http GET request is caused by browser's BACK button.

Login Page PageRequestManagerServerErrorException on ASP.NET The status code returned from the server was: 0

We are getting strange error with our login page. It is working on almost all client but one of the client has following exception:-
When we press login button, it goes in wait mode ( in IE as well as Chrome)
When we used fiddler, it shows no response and at last it shows Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 0 in Console panel.
The login box is wraped in Update Panel that again wrapped in Script manager.
Can anybody guess whats exact issue or how do we find it.

OnDisconnected does not fire with reloading the page

im using signalr-rc2 and use it for cross-domain long-polling calls on IIS7(not express)
everything works fine execpt OnDisconnected on server-side
when i hit the close button on browser(firefox or chrome) OnDisconnected invoked but
when i refresh the browser tab,,OnDisconnected does not invoked
however i test it on a small project an it works fine totally
my question is whats the diffrence between reloading browser page and closing it
i wait almost 15 minutes for delay of IIS to realize client disconnection but nothing happens

I found the problem it was two html tag in document
caused by asp.net mvc view render(i forgot to return partialview instead of view in action method)

Browser hangs after HTTP POST from Acrobat Reader

The Adobe Acrobat browser plug-in is being used to accept form input from a user. After a user has completed the PDF form and clicked its submit button, the form data is posted to an Asp.Net page that accepts the data, stores it and returns a message as HTML.
This works fine in Acrobat Reader in Firefox. Within Internet Explorer, our targeted browser, after the PDF form has been submitted, the data is accepted by Asp.Net, saved to disk and, by way of a packet sniffer, I can see that the HTML response is served, but IE hangs after the PDF is unloaded like it's trying to load the response, but never does.
I've determined that the problem occurs with IIS6 and IIS7, with or without SSL, on Windows XP and 7, and with Adobe Reader 9 and 10; what considerations am I overlooking?

This behavior seems to occur in Internet Explorer when the Acrobat Reader plug-in sends the HTTP POST followed by an alert dialog box being invoked with something like the following:
app.alert({
cMsg: "Error! Try again!",
cTitle: "Acme Testing Service"
});
The issue seems to stem from running a script after the HTTP POST has been sent; reordering the sequence of events has resolved the issue I was experiencing.

Resources