[ 
https://issues.apache.org/jira/browse/COUCHDB-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151269#comment-14151269
 ] 

ASF GitHub Bot commented on COUCHDB-2340:
-----------------------------------------

GitHub user ocelotpotpie opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/67

    COUCHDB-2340 - Remove extra subnav breadcrumb.

    This removes the extra "_changes" breadcrumb in the databases subnav, as 
well as a few minor style tweaks to get the database name to line up all 
nice-like.
    
    Tested for regression in:
    Safari 7.0.6
    Chrome 37.0.2062.124
    Firefox 32.0.2
    An iPhone running iOS 8 (Just because).

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

    $ git pull https://github.com/ocelotpotpie/couchdb-fauxton 
COUCHDB-2340-remove-extra-subnav-breadcrumb

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

    https://github.com/apache/couchdb-fauxton/pull/67.patch

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

    This closes #67
    
----
commit 5970a15ccc8f672fe1be4f06c1eb60877fef5ab6
Author: Christian Hogan <[email protected]>
Date:   2014-09-29T00:06:09Z

    COUCHDB-2340 - Remove extra subnav breadcrumb.

----


> Redundant / unnecessary breadcrumb in database subnav header
> ------------------------------------------------------------
>
>                 Key: COUCHDB-2340
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2340
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Christian Hogan
>
> Database subnav has section breadcrumbs, as well as an active / highlighted 
> subnav item. The breadcrumb ends up being redundant and it's limiting room in 
> the subnav header. Breadcrumb in the subnav header should be removed and 
> context should rely on the subnav items below.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to