Bug 1015380 - Inconsistent vertical alignment in Time and External Tracker tables
Summary: Inconsistent vertical alignment in Time and External Tracker tables
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 4.4
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: 4.4
Assignee: Simon Green
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-04 04:48 UTC by Jason McDonald
Modified: 2018-12-09 06:29 UTC (History)
3 users (show)

Fixed In Version: 4.4.1010
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-03 23:33:04 UTC

Attachments (Terms of Use)
Screenshot showing misaligned table fields (50.64 KB, image/png)
2013-10-04 04:48 UTC, Jason McDonald 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jason McDonald 2013-10-04 04:48:34 UTC 
Created attachment 807378 [details]
Screenshot showing misaligned table fields

Description of problem:
When viewing a bug, the Time and External Tracker tables do not vertically align all fields consistently.

In particular, the Current Est, %Complete and Gain fields in the Time table are top aligned while other fields appear to be center aligned.  Simialrly, the Last Updated fields of the External Tracker table is bottom aligned while other fields appear to be top aligned.

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

How reproducible:
Always

Steps to Reproduce:
1. Open https://bugzilla.redhat.com/show_bug.cgi?id=965433
2. View the Time and External Tracker tables -- see attached screen shot

Actual results:
Inconsistent vertical alignment

Expected results:
Consistent vertical alignment (perhaps vertical-center alignment would look best).

Additional info:
none
Comment 2 Simon Green 2013-11-03 23:33:04 UTC 
This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.

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