Bug 1062167 - new UI is to high
Summary: new UI is to high
Keywords:
Status: CLOSED DUPLICATE of bug 1019319
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-06 11:42 UTC by Martin Kudlej
Modified: 2018-02-06 00:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-06 22:35:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Martin Kudlej 2014-02-06 11:42:40 UTC
Description of problem:
If you compare old and new UI, in new UI you can see less information on screen. It is because there are too big padding and margins. I use these modifications of new beaker pages:

  h1, h2, h3 {
        line-height: 10px !important;
      }

      .table th, .table td {
        padding: 2px !important;
      }
      .page-header {
        margin-bottom: 5px !important;
      }
      .form-search {
        margin-bottom: 5px !important;
        margin-top: 5px !important;
      }
      .pagination {
        margin-top: 5px !important;
        margin-bottom: 5px !important;
      }
I think it is not necessary to have that big paddings and margins because most of beaker users don't use touch-screen. 

Version-Release number of selected component (if applicable):
Version 0.15.3

How reproducible:
100%

Actual results:
Paddings and margins are too big and that's why there is less information visible on screen.

Expected results:
Paddings and margins are smaller than now.

Comment 2 Nick Coghlan 2014-02-06 22:35:04 UTC
The increased spacing is deliberate, based on the general results of interface usability research. However, the change has highlighted a number of deficiences in the Beaker UI's use of vertical space, which are discussed in bug 1019319.

*** This bug has been marked as a duplicate of bug 1019319 ***


Note You need to log in before you can comment on or make changes to this bug.