<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/tag/microsoft.">
<title>Public marks with tag microsoft.</title>
<description>Public marks with tag microsoft.</description>
<link>http://blogmarks.net/marks/tag/microsoft.</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/greut/mark/1057718184"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/greut/mark/1057718184">
<title>How to build a cross-browser history management system - Tales from the Evil Empire</title>
<link>http://weblogs.asp.net/bleroy/archive/2007/09/07/how-to-build-a-cross-browser-history-management-system.aspx</link>
<description>&lt;blockquote&gt;&lt;p&gt;The main trick that history managers use is to have the browser believe the user navigated to a new url without the current page and all its JavaScript and DOM state being thrown away. The only part of the url that enables such a thing is the hash part. The hash part is what comes at the end of the url after a pound (#) sign. The original intent of this part of the url was to allow for navigation inside of the document. You would put a special named, href-less anchor tag in your document, and then navigating to #nameOfTheAnchor would just scroll the anchor into view. The page doesn't get reloaded, but it does enter the browser history.&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;YUI Browser History Manager does that for you, but lack of documenting how it works under the hood.&lt;/p&gt;</description>
<dc:date>2008-03-02T14:00:35Z</dc:date>
<dc:author>greut</dc:author>
<dc:subject>javascript, history, yui, yahoo, microsoft.</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://weblogs.asp.net/bleroy/archive/2007/09/07/how-to-build-a-cross-browser-history-management-system.aspx"><img border="0" src="http://blogmarks.net/screenshots/2008/03/02/cbbc99a8016bb364a00d5ef246cfa8f2.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://weblogs.asp.net/bleroy/archive/2007/09/07/how-to-build-a-cross-browser-history-management-system.aspx">How to build a cross-browser history management system - Tales from the Evil Empire</a></h4>
 
by <a href="http://blogmarks.net/user/greut">greut</a> 
<div class="description"><blockquote><p>The main trick that history managers use is to have the browser believe the user navigated to a new url without the current page and all its JavaScript and DOM state being thrown away. The only part of the url that enables such a thing is the hash part. The hash part is what comes at the end of the url after a pound (#) sign. The original intent of this part of the url was to allow for navigation inside of the document. You would put a special named, href-less anchor tag in your document, and then navigating to #nameOfTheAnchor would just scroll the anchor into view. The page doesn't get reloaded, but it does enter the browser history.</p></blockquote><p>YUI Browser History Manager does that for you, but lack of documenting how it works under the hood.</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/history">history</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/yui">yui</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/yahoo">yahoo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microsoft.">microsoft.</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057718184">Copy</a> | 
<a href="http://blogmarks.net/link/2688760">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>