GitHub user robertkowalski opened a pull request:
https://github.com/apache/couchdb/pull/241
Fauxton: fix scrollbar-issue - COUCHDB-2234
This is a sliceoff from #225 where I try to fix the issue with the
scrollbars.
- Try to honor borders in calculating the width
- Adjust magic numbers to new widths of the left area
- Refactor the header/api-url section
- Removing the maximum widths of 1400px and 1500px, which caused
vertical scrollbars to appear at 1400px (which is on top of the
page content, some hundred pixels away from the left side on
large screens) on a system like windows
COUCHDB-2234
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robertkowalski/couchdb scrollbars
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb/pull/241.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 #241
----
commit 138697316690e3ed22e6f4828b742a2b8f167ed5
Author: Robert Kowalski <[email protected]>
Date: 2014-05-29T19:08:05Z
remove whitespace
commit 6099cc02c50f84c5cd051df917feb1c3cc09757c
Author: Robert Kowalski <[email protected]>
Date: 2014-05-29T19:09:45Z
remove unused configuration for resizable container
commit be3b7d5ed441a1c8ee47e719cadde24222a62c22
Author: Robert Kowalski <[email protected]>
Date: 2014-05-31T13:14:32Z
Fauxton: fix scrollbar-issue - COUCHDB-2234
- Try to honor borders in calulating the width
- Adjust magic numbers to new widths of the left area
- Refactor the header/api-url section
- Removing the maximum widths of 1400px and 1500px, which caused
vertical scrollbars to appear at 1400px (which is on top of the
page content, some hundred pixels away from the left side on
large screens) on a system like windows
COUCHDB-2234
----
---
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.
---
