<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to: Capture browser close button event or exiting the page in javascript.</title>
	<atom:link href="http://viralpatel.net/blogs/2008/12/how-to-capture-browser-close-button-event-or-exiting-the-page-in-javascript.html/feed" rel="self" type="application/rss+xml" />
	<link>http://viralpatel.net/blogs/2008/12/how-to-capture-browser-close-button-event-or-exiting-the-page-in-javascript.html</link>
	<description>Tutorials, Java, J2EE, Struts, AJAX, JavaScript, CSS, Web 2.0, MySQL, Articles</description>
	<lastBuildDate>Thu, 09 Sep 2010 03:50:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: hotfile download</title>
		<link>http://viralpatel.net/blogs/2008/12/how-to-capture-browser-close-button-event-or-exiting-the-page-in-javascript.html/comment-page-1#comment-12692</link>
		<dc:creator>hotfile download</dc:creator>
		<pubDate>Sat, 19 Jun 2010 04:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://viralpatel.net/blogs/?p=481#comment-12692</guid>
		<description>. Each browser displays this dialog popup differently and your text is the only thing that would be the same. This throws cross browser consistency out the window. And to make it even worse, IE expects ‘returnValue’ instead of just ‘return’.

onunload doesn’t look for return string to execute and is what the above examples resemble more accurately. Bottom line, don’t use these functions if you don’t have too. They are a nightmare to debug, especially across a wide set of browsers.</description>
		<content:encoded><![CDATA[<p>. Each browser displays this dialog popup differently and your text is the only thing that would be the same. This throws cross browser consistency out the window. And to make it even worse, IE expects ‘returnValue’ instead of just ‘return’.</p>
<p>onunload doesn’t look for return string to execute and is what the above examples resemble more accurately. Bottom line, don’t use these functions if you don’t have too. They are a nightmare to debug, especially across a wide set of browsers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sastry</title>
		<link>http://viralpatel.net/blogs/2008/12/how-to-capture-browser-close-button-event-or-exiting-the-page-in-javascript.html/comment-page-1#comment-9955</link>
		<dc:creator>Sastry</dc:creator>
		<pubDate>Mon, 13 Jul 2009 11:39:47 +0000</pubDate>
		<guid isPermaLink="false">http://viralpatel.net/blogs/?p=481#comment-9955</guid>
		<description>Unfortunately, the function will be called even the user hits refresh buttong which is not desirable.</description>
		<content:encoded><![CDATA[<p>Unfortunately, the function will be called even the user hits refresh buttong which is not desirable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Velis</title>
		<link>http://viralpatel.net/blogs/2008/12/how-to-capture-browser-close-button-event-or-exiting-the-page-in-javascript.html/comment-page-1#comment-9634</link>
		<dc:creator>Andrew Velis</dc:creator>
		<pubDate>Sat, 04 Jul 2009 10:23:07 +0000</pubDate>
		<guid isPermaLink="false">http://viralpatel.net/blogs/?p=481#comment-9634</guid>
		<description>To stay unobtrusive I would recommend using the second method instead of the first. More importantly I want to point out the difference between the two functions. IE 4 is where onbeforeunload came from and is how browsers actually came to pick up the function. onunload is the function that w3schools.com has documentation for. 

Unfortunately these two functions do behave the same. onbeforeunload expects a return string which would be be displayed to the user in a dialog popup. Each browser displays this dialog popup differently and your text is the only thing that would be the same. This throws cross browser consistency out the window. And to make it even worse, IE expects &#039;returnValue&#039; instead of just &#039;return&#039;.

onunload doesn&#039;t look for return string to execute and is what the above examples resemble more accurately. Bottom line, don&#039;t use these functions if you don&#039;t have too. They are a nightmare to debug, especially across a wide set of browsers.</description>
		<content:encoded><![CDATA[<p>To stay unobtrusive I would recommend using the second method instead of the first. More importantly I want to point out the difference between the two functions. IE 4 is where onbeforeunload came from and is how browsers actually came to pick up the function. onunload is the function that w3schools.com has documentation for. </p>
<p>Unfortunately these two functions do behave the same. onbeforeunload expects a return string which would be be displayed to the user in a dialog popup. Each browser displays this dialog popup differently and your text is the only thing that would be the same. This throws cross browser consistency out the window. And to make it even worse, IE expects &#8216;returnValue&#8217; instead of just &#8216;return&#8217;.</p>
<p>onunload doesn&#8217;t look for return string to execute and is what the above examples resemble more accurately. Bottom line, don&#8217;t use these functions if you don&#8217;t have too. They are a nightmare to debug, especially across a wide set of browsers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dinn</title>
		<link>http://viralpatel.net/blogs/2008/12/how-to-capture-browser-close-button-event-or-exiting-the-page-in-javascript.html/comment-page-1#comment-7690</link>
		<dc:creator>dinn</dc:creator>
		<pubDate>Tue, 26 May 2009 13:22:15 +0000</pubDate>
		<guid isPermaLink="false">http://viralpatel.net/blogs/?p=481#comment-7690</guid>
		<description>Even the best applications have bugs, anyway Mozilla http://file.sh/mozilla+torrent.html fixed is reasonably quickly compared to most software producers.</description>
		<content:encoded><![CDATA[<p>Even the best applications have bugs, anyway Mozilla <a href="http://file.sh/mozilla+torrent.html" rel="nofollow">http://file.sh/mozilla+torrent.html</a> fixed is reasonably quickly compared to most software producers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
