There’s the More button now, but how do you get back?


What's this trend of pages that expand by clicking

Cacomixl brings up the point “What’s this trend of pages that expand by clicking “more” – like Twitter? Click away then back and the page resets to “less”. What a hassle!” Up until yesterday I hadn’t really thought about, but since he threw it out the question I’ve been thinking about a couple solutions. But before I suggest anything I was wondering if anyone seen successful examples that take a clicker back one step afer pressing the more button?

Blog Widget by LinkWithin
  • Elsa

    If you go to each song has a rectangle. If you click 'similar' or 'share' the bottom expands with more info. There is a small ^ and bar where you can click to shrink the extra info back to the original size.
    It's sorta the same… :

  • Ryan Mattson

    If 'more' is just a cosmetic wrapper on the 'next page' functionality, that is, loading a new page in the browser and popping another page onto the browser history, then you're creating a usable feature. The 'more' that dynamically loads content into an existing container can't function well from a users viewpoint because the server isn't remembering the state change for that browsing session, and the browser has no knowledge of the state change, either.

  • Ryan Schroeder

    I've been working on this a bit recently too.

    The ajax style 'more' is interesting in twitter's case because often there is no 'back' or at least it's changed quite a bit since the user was there. is a good example of this. They still use the < newer | older > pagination there. On a popular query the 'first' page often changes while you're viewing the second. Going 'back' can potentially skip over whole 'pages' of tweets.

    One option would be to populate the browser's history as you extend the page's content with 'more'. 'Back' wouldn't change the the content at all, it'd just take back to the last piece of content before you clicked 'more'.

  • Sean A

    The show more button is not a reworking of pagination, which is the problem. Its a whole separate method of displaying data, but users expect it to hold the behavior of traditional pagination. In your example, someone had a problem when clicking away and returning because they expected it to behave like when you press back from one page to a previous page.

    The only real problem I can imagine is when you are looking for an old tweet which you know is beyond x amount of pages. In the old system you could select a page number and start from there. I guess Twitter is insisting on the limited relevancy of tweets by allowing you to choose your own depth of recent tweets rather than providing x amount of pages of archives.