GitHub user robertkowalski opened a pull request:

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

    Componentize footer

    Take the elements that were all baked into all-docs-list
    and inject them into the all-docs-list. This enables us to have
    a separate footer component in the layout which can be initialized
    without the all-docs-list viewobject.
    
    This enables us to remove the `position: fixed` from the footer
    and use `position: absolute`. Without having the element
    `position: fixed;` we do not need to calculate it's width via JS
    and can apply a css based pane layout.
    
    Part of: COUCHDB-2471

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

    $ git pull https://github.com/robertkowalski/couchdb-fauxton 
COUCHDB-2471-footer

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

    https://github.com/apache/couchdb-fauxton/pull/173.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 #173
    
----
commit a40d493f990eec87a307ec3985eecc73dfd6ef92
Author: Robert Kowalski <[email protected]>
Date:   2014-11-27T14:30:26Z

    Componentize footer
    
    Take the elements that were all baked into all-docs-list
    and inject them into the all-docs-list. This enables us to have
    a separate footer component in the layout which can be initialized
    without the all-docs-list viewobject.
    
    This enables us to remove the `position: fixed` from the footer
    and use `position: absolute`. Without having the element
    `position: fixed;` we do not need to calculate it's width via JS
    and can apply a css based pane layout.
    
    Part of: COUCHDB-2471

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to