Re:Backbone.js 0.5.0 Released (with pushState)
by odiroot on Friday July 01, 2011 @04:18PM
(#2719991)
Or you could use progressive JavaScript, AFAIK. Make your every link a first class citizen (with it's own view) and for supported browsers replace links' default action with content switching (without reloading) using JS requests.
Of course that's a bit harder since your views need to respond in a different manner to casual GETs and AJAX requests.
Re:Backbone.js 0.5.0 Released (with pushState)
by encoderer on Friday July 01, 2011 @04:26PM
(#2720017)
Which really should be trivial using most modern 3-Tier frameworks. They universally have a concept of "layout" vs "template" so in a pseudocode logic, all you need to do is tap into the render method and swap out an empty layout when responding to an XHR request.
Re:Backbone.js 0.5.0 Released (with pushState)
by odiroot on Friday July 01, 2011 @06:12PM
(#2720349)
Exactly, however one can argue the number of your test cases (and cache entries) doubles. Still I think it's an elegant solution.
Re:Backbone.js 0.5.0 Released (with pushState)
by zmanji on Friday July 01, 2011 @03:56PM
(#2719913)
How can there be SEO issues? I thought the whole point of pushState was to allow AJAX loading of content (without refresh) but not break URLS with #!.
Re:Backbone.js 0.5.0 Released (with pushState)
by alecperkins on Saturday July 02, 2011 @09:58AM
(#2721615)
There aren't if used correctly. The SO questioner has a misunderstanding of how the history API and the hashbang scheme are supposed to work.
pushState's SEO issues.