How to build a cross-browser history management system - Tale...
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
URL Tag Cloud
- Ajax
- , javascript
- , history
- , Browser
- , asp.net
- , web
- , browsers
- , programming
- , Scripting
- , Dev
- , crossbrowser
- , furl
- , dotnet
- , articles
- , develop
- , ui
- , development
- , reference
- , webdev
Bookmark History
Saved by 9 people (0 private), first by anonymouse user on 2007-11-05
- Samgoody on 2009-04-06 - Tags Scripting , Javascript , Tips , Backbutton
- Aggtaa on 2008-12-15 - Tags programming , ajax , javascript , web , browser
- Tomjoad on 2008-02-29 - Tags ajax , asp.net , browser , history
- Rockmaple on 2007-12-05 - Tags no_tag
- Wtnabe on 2007-11-05 - Tags develop , javascript , web
Public Sticky notes
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.
Highlighted by rockmaple


Public Comment
on 2007-11-05 by wtnabe