<?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: IE8 HTML 5 Ajax Page Navigations</title>
	<atom:link href="http://ajaxian.com/archives/ie8-html-5-ajax-page-navigations/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/ie8-html-5-ajax-page-navigations</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: eyelidlessness</title>
		<link>http://ajaxian.com/archives/ie8-html-5-ajax-page-navigations/comment-page-1#comment-265879</link>
		<dc:creator>eyelidlessness</dc:creator>
		<pubDate>Wed, 16 Jul 2008 20:24:53 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ie8-html-5-ajax-page-navigations#comment-265879</guid>
		<description>@Jordan1:
I agree that some protection of the user is in order, but restricting to onclick is probably problematic (I know it&#039;s problematic with popup blockers already). Any XHR request should allow populating history, definitely (or onsubmit equivalents for things like livesearch can&#039;t be in the history). There might even be a rationale for key events, as a good interface should also support keyboard navigation. Ultimately it might be safe to allow any native event plus XHR to populate history, but I haven&#039;t really thought that through completely.</description>
		<content:encoded><![CDATA[<p>@Jordan1:<br />
I agree that some protection of the user is in order, but restricting to onclick is probably problematic (I know it&#8217;s problematic with popup blockers already). Any XHR request should allow populating history, definitely (or onsubmit equivalents for things like livesearch can&#8217;t be in the history). There might even be a rationale for key events, as a good interface should also support keyboard navigation. Ultimately it might be safe to allow any native event plus XHR to populate history, but I haven&#8217;t really thought that through completely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan1</title>
		<link>http://ajaxian.com/archives/ie8-html-5-ajax-page-navigations/comment-page-1#comment-265873</link>
		<dc:creator>Jordan1</dc:creator>
		<pubDate>Wed, 16 Jul 2008 13:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/ie8-html-5-ajax-page-navigations#comment-265873</guid>
		<description>I wonder if there are &quot;popup blocker&quot; equivalents for this feature to prevent pr0n sites from filling the back button history with more pr0n. Maybe something like, a history entry is only created if it is from an &quot;onclick&quot;.</description>
		<content:encoded><![CDATA[<p>I wonder if there are &#8220;popup blocker&#8221; equivalents for this feature to prevent pr0n sites from filling the back button history with more pr0n. Maybe something like, a history entry is only created if it is from an &#8220;onclick&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

