Sometimes whilst bored I read old xkcd's annd although I know all the comics, I do from time to time discover a title text I hadn't seen before. This time I came across
Which had the title text: "Maybe we should give up on the whole idea of a 'back' button. 'Show me that thing I was looking at a moment ago' might just be too complicated an idea for the modern web."
This made me think, would it be a good UX practice to make the back button scroll up the page instead of going back a normal URL? And have a refresh load up that specific place in the infinite list instead of the top of the list. As far as I can see there is no technical reason not to do this, yet I haven't seen this implemented anywhere, so I am hereby asking whether you guys know of anybody who researched and/or implemented this? And if not just for opinions which disadvantages this approach could have. (Or a simple 'Yes you should do that!' if none of the before applies).
You are on BBC.co.uk and go to Facebook. You scroll down a couple of pages, when you hit the back button, instead of going back to BBC you just scroll up one page. Till you get up till the first, after which you would after all just go back. When you copy the URL and bookmark it you are able to find the post you were just looking at (and still scroll up for more posts up till the most recent one).
With the History API in the browser you can change the URL at any time, so when you would scroll down you would see the URL change the ?p=n (or in the above example t=i) part all the time. Going back would thus just go back to the previous URL state. (The facebook example would require a simple interaction between replaceStates all the time and a single pushState per page).
No comments:
Post a Comment