couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From michellephung <>
Subject [GitHub] couchdb-fauxton pull request: 2427 ux viewing replication document...
Date Fri, 31 Oct 2014 22:33:55 GMT
GitHub user michellephung opened a pull request:

    2427 ux viewing replication documents loses context

    When navigating back from a viewing/editing a document, the user expects to 'go back'
to the previous page they came from. Currently, 'back' button will always go back to all_docs
of the document's database, which may not be the the previous page the user came from.
    1. I changed the 'back to _all_docs' button to read 'back', so depending what page sent
you to the documents page, you aren't forced to go back to _all_docs.
    2. I changed the 'goback' function, so if you have been inside fauxton for more than one
page, you'll be redirected there via 'window.history.back()', if pasted the page into your
browser, the back button will take you back to _all_docs of the database of the document you
were viewing
    3. I added a history array to the router that keeps that last 2 links you visited. 

You can merge this pull request into a Git repository by running:

    $ git pull 2427-UX-viewing-replication-documents-loses-context

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #121
commit 2035141303435a6fafd6507746e0951eef5e341f
Author: Michelle Phung <>
Date:   2014-10-31T22:11:25Z

    2427 -Fixes UX View replication doc loses context

commit 4a7aec9f6b5e14330d292468d82354dff8151b06
Author: Michelle Phung <>
Date:   2014-10-31T22:13:43Z

    changed length of history array


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message