Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Backbone.js 0.5.0 Released (with pushState)

blog.documentcloud.org

Post reply on HN
Print view View original

31–38 of 38 posts

Re: Backbone.js 0.5.0 Released (with pushState)

#31

Post by bphogan »

jashkenas wrote: post #2

I'd be curious to hear from anyone who thinks that this sort of parallel hashchange/pushState support is a bad idea. It should prove to be controversial at the least. * http://www.documentcloud.org/public/#search/guantanamo * http://www.documentcloud.org/public/search/guantanamo People who don't care much about Internet Explorer support often say to just use pushState, and let IE users endure full page refreshes ...…

I'd just like to see a little better documentation on this in the Backbone docs. The documentation you currently have says I'll need to alter the backend, but it's not exactly clear what the changes to the backend would need to be. Do I need to implement /new and /edit on my server to make Backbone's pushSate work, or do I need them implemented to provide for a graceful fallback? It's a little confusing as written so I had to just code something up to see what happened.

Re: Backbone.js 0.5.0 Released (with pushState)

#32

Post by jashkenas »

bphogan wrote: post #31
jashkenas wrote: post #2

I'd be curious to hear from anyone who thinks that this sort of parallel hashchange/pushState support is a bad idea. It should prove to be controversial at the least. * http://www.documentcloud.org/public/#search/guantanamo * http://www.documentcloud.org/public/search/guantanamo People who don't care much about Internet Explorer support often say to just use pushState, and let IE users endure full page refreshes ...…

I'd just like to see a little better documentation on this in the Backbone docs. The documentation you currently have says I'll need to alter the backend, but it's not exactly clear what the changes to the backend would need to be. Do I need to implement /new and /edit on my server to make Backbone's pushSate work, or do I need them implemented to provide for a graceful fallback? It's a little confusing as written so…

Thanks for the tip. How does this look to you?

https://github.com/documentcloud/backbone/commit/3a56d366865...

Re: Backbone.js 0.5.0 Released (with pushState)

#33

Post by premchai21 »

jashkenas wrote: post #2

I'd be curious to hear from anyone who thinks that this sort of parallel hashchange/pushState support is a bad idea. It should prove to be controversial at the least. * http://www.documentcloud.org/public/#search/guantanamo * http://www.documentcloud.org/public/search/guantanamo People who don't care much about Internet Explorer support often say to just use pushState, and let IE users endure full page refreshes ...…

I'm suspicious of certain possible scenarios here. Someone without the history state API (e.g., an Internet Explorer 8 user) who wants to send out links winds up publishing fragment-based links (with all the scattered interoperability breakage thereof), but others get and publish full(-flavor) links. Then someone finds that with more restrictive JavaScript settings, some of the links work and some of them don't, or bookmarks two references to the same thing, or…

It seems like it would have potential for confusion, but it strongly depends on the application and its context. It's possible for the author to partially work around this by providing what amounts to an extra URI indicator (similar to “permalink” markers in blogs and other time-dependent views of content stores), but this is awkward. (Is there an add-on library for that, for that matter?)

Re: Backbone.js 0.5.0 Released (with pushState)

#34

Post by alecperkins »

zmanji wrote: post #22
Hipchan wrote: post #21

http://stackoverflow.com/questions/6193858/pushstate-and-seo pushState's SEO issues.

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 #!.

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.

Re: Backbone.js 0.5.0 Released (with pushState)

#35

Post by bphogan »

jashkenas wrote: post #32
bphogan wrote: post #31

Earlier quoted context omitted.

I'd just like to see a little better documentation on this in the Backbone docs. The documentation you currently have says I'll need to alter the backend, but it's not exactly clear what the changes to the backend would need to be. Do I need to implement /new and /edit on my server to make Backbone's pushSate work, or do I need them implemented to provide for a graceful fallback? It's a little confusing as written so…

Thanks for the tip. How does this look to you? https://github.com/documentcloud/backbone/commit/3a56d366865...

It looks like a good start - I'll follow up on github. Thanks!

Re: Backbone.js 0.5.0 Released (with pushState)

#37

Post by Jase »

jashkenas wrote: post #2

I'd be curious to hear from anyone who thinks that this sort of parallel hashchange/pushState support is a bad idea. It should prove to be controversial at the least. * http://www.documentcloud.org/public/#search/guantanamo * http://www.documentcloud.org/public/search/guantanamo People who don't care much about Internet Explorer support often say to just use pushState, and let IE users endure full page refreshes ...…

This is probably the best articulated post on why hash-based URLs suck: http://danwebb.net/2011/5/28/it-is-about-the-hashbangs
Post reply on HN