On 6 January 2011 15:52, Walter Lee Davis <[email protected]> wrote: > On Jan 5, 2011, at 7:18 AM, Mauro wrote: > >> but it seems that the new javascript api history.pushState doesn't >> work as well as jquery.ba-bbq.js > > What are you basing this on? pushState only works in browsers that support > it, so Safari and a few other cutting-edge browsers, and nothing else, IIRC. > I would guess that jQuery does some work-arounds to support lots more > browsers, but I'm not sure if there are libraries available yet that use the > native event if available and degrade to support functions where it's not. > That would be cool. > > If you look at the latest Railscast about this (couple weeks ago?) it shows > how to make a system that degrades nicely to regular full reloads if > pushState isn't there to do the sub-page-reloads-with-history.
I've seen that railscast, I'm using chrome which support pushState. The problem is that ajax history with paginate works but if you, for example, go to a site www.google.it or whatever internet site and then push browser back button the page showed isn't an html page, but it seems a text page. Try. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
