undefined | Better HN

0 pointsepidemian12y ago0 comments

The thing is that it has to work cross-browser. If an IE user copies an URL with both a fragment query string and a real query string and then shares it with a Firefox user, the URL should resolve to the same thing (and the same thing the other way around).

Not impossible by any means, but, as Jeremy points out, it involves subtle details :)

0 comments

jashkenas12y ago

Right-o. PushState-supporting users copying URLs and sending them to IE8 and IE9 folks is one thing, as is the opposite direction.

In addition, some folks currently like to mount their Backbone.js applications at a root URL that contains a query string, for example:

    todolist.com/app?org=nsa#location

thedufer12y ago

> some folks currently like to mount their Backbone.js applications at a root URL that contains a query string

That seems like the root of the problem. It seems like querystrings could otherwise be solved, but this case would certainly introduce a problem for pushState-incompatible browsers.

Is there a reason this kind of app root URL isn't considered bad practice that doesn't need to be supported? Everything about it seems wrong - now you're trying to put part of the path after the querystring.

smacktoward12y ago

"Doctor, it hurts when I do this."

"Then don't do that."

altcognito12y ago

I love backbone, and it works well for us. We hacked in support for full paths and query parameters and will likely end doing full page reloads for IE8/IE9 (IE10 will support push state anyway)

It seems mighty unfair that we can't have nice things because Microsoft took so long to roll out push state.

byroot12y ago

Well it's les simple that I though but it's still seems doable. I'll probably try to submit a PR about that. Is there any previous PR or issue that I should rea first ?

j / k navigate · click thread line to collapse