history.js

I just stumbled on a note from the abandoned project [History.js](https://github.com/browserstate/history.js/): > Despite History.js being one of the most popular JavaScript libraries there is, and has been used by even multi-million-user companies in its time - the reality of economy and company practices seems to be that companies prefer to fork their own internal versions and fix locally with their own devs rather than fund open-source maintainers what they would pay their own devs to make things better for everyone, including themselves, which would be cheaper - but no, that would require too many tiers of company approval that don't understand the need. > As such, if you are an open-source developer, I'd recommend just working on open-source projects that are paid for by your own consulting work or your own company (e.g. every succes

I'm not sure if this announcement changes anything. The bottom line is to make apps for the end user. Google is simply saying that those best practices are now crawlable in a way that is very mature. The same rules still apply. A simple guide can be found here: https://developers.google.com/webmasters/ajax-crawling/. Although I suspect it needs to be updated since its from 2012. If you create an application, make sure it alters the URL when applicable. For simple apps, the following repos will be useful: The old way, that still works: https://github.com/asual/jquery-address The better way, preferred: https://github.com/browserstate/history.js or https://github.com/defunkt/jquery-pjax.... not sure which is better to be honest. Feel free to chime in.

I have a couple quibbles with the article, notably: > Special support for Ajax URLs being raised as an industry standard and a best practice, whereas it's a Google hack of a solution. HTML5 history.pushState[0] is the proper standard solution, with a nice polyfill[1] [0]: https://developer.mozilla.org/en-US/docs/DOM/Manipulating_th... [1]: https://github.com/balupton/history.js

You should check this out: https://github.com/balupton/History.js

I recently came across history.js https://github.com/balupton/History.js/ which will use pushState where supported and falls back to hashbangs otherwise. It was overkill for my project, (we were already relying on several other advanced html5 features so most users should have pushState) but it certainly seems useful.

As far as I know, the proper way to create a modern web app to deal with location.hash fallback and pushState, replaceState etc is to use https://github.com/balupton/History.js . Comments/Corrections are welcome.

Would be cool if you added pushState or /#/ history. You can for example use history.js: https://github.com/balupton/history.js

Because the app is in an iFrame, you can just use regular linked files and then the back button works as expected. If you do that though, there are a few other issues - you may have to account for pages that do/don't have the Facebook signed_request post data - i.e. you probably need to store it in a session or cookie (and deal with the relevant IE7 cookie + iFrame issues by settings P3P header if you support IE7. Can't remember offhand if it is a problem in IE8.) Obviously more complex apps where navigation is handled through AJAX get tricky when you can't access the container frame. Maybe look into history.js (https://github.com/balupton/History.js/) and see if it works in a Facebook app?

Try this : https://github.com/balupton/History.js

The hashbang is a big gory mess and glorified for all the wrong reasons. Mostly it brakes best practices and destroys the chance for graceful upgradation and degradation. What is truly amazing is that there actually are other solutions that still offer the best practices like graceful upgradation and degradation with less effort. This article goes into the issues and the alternatives: https://github.com/balupton/history.js/wiki/Intelligent-Stat...