Why JavaScript web applications should embrace traditional URLs

Post by epidemian » Wed, Jul 17, 2013, 3:22 PM UTC

byroot wrote: post #10

jashkenas wrote: post #6

The fundamental problem with attempting to transparently support querystrings on the client-side -- touched on a bit in this article, but not explained completely, is this: Querystrings are a server-side convention for URLs containing parameters -- the browser doesn't traditionally parse them. If you ask for document.location.search, you'll get back an opaque string containing the query part that you'll have to parse…

> now you have the possibility to have to merge two different sources of query string Not really: if hashMode and queryStringInHash parseQueryStringFromHash else parseRealQueryString You don't have to merge. Just if you modify the query string and are in "hashMode" then just push the "real querystring" elements you parsed first into the "hashquery string".

Post by vinceguidry » Wed, Jul 17, 2013, 3:29 PM UTC

4ad wrote: post #12

vinceguidry wrote: post #7

I'm getting rank sick of the growing number of websites killing the functionality of the back button. That, combined with Chromes senseless refusal to implement opening clicked urls that are on another domain in a new tab, means I'm often forced to click-and-hold the back button to get somewhere. Incredibly annoying.

I don't understand at all what you mean. To open pages in a new tab you middle click the link. Pages that automatically open in new tab are annoying. If Chrome has something that stops this, I'm extremely happy. The user should control whether a page opens in a new tab or not, and indeed the user can do that -- left click or middle click.

Post by [deleted] » Wed, Jul 17, 2013, 3:43 PM UTC

vinceguidry wrote: post #13

4ad wrote: post #12

Earlier quoted context omitted.

I don't understand at all what you mean. To open pages in a new tab you middle click the link. Pages that automatically open in new tab are annoying. If Chrome has something that stops this, I'm extremely happy. The user should control whether a page opens in a new tab or not, and indeed the user can do that -- left click or middle click.

I'm on a Mac, I don't have a middle mouse button.

Post by jashkenas » Wed, Jul 17, 2013, 4:00 PM UTC

epidemian wrote: post #11

byroot wrote: post #10

Earlier quoted context omitted.

> now you have the possibility to have to merge two different sources of query string Not really: if hashMode and queryStringInHash parseQueryStringFromHash else parseRealQueryString You don't have to merge. Just if you modify the query string and are in "hashMode" then just push the "real querystring" elements you parsed first into the "hashquery string".

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 :)

    todolist.com/app?org=nsa#location

Post by moogleii » Wed, Jul 17, 2013, 4:18 PM UTC

4ad wrote: post #12

vinceguidry wrote: post #7

I'm getting rank sick of the growing number of websites killing the functionality of the back button. That, combined with Chromes senseless refusal to implement opening clicked urls that are on another domain in a new tab, means I'm often forced to click-and-hold the back button to get somewhere. Incredibly annoying.

I don't understand at all what you mean. To open pages in a new tab you middle click the link. Pages that automatically open in new tab are annoying. If Chrome has something that stops this, I'm extremely happy. The user should control whether a page opens in a new tab or not, and indeed the user can do that -- left click or middle click.