Bug 598833 - should the dates in the revision history be right aligned ?
should the dates in the revision history be right aligned ?
Product: Publican
Classification: Community
Component: publican (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Jeff Fearn
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-06-02 02:45 EDT by Dana Mison
Modified: 2010-11-23 23:17 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-11 23:51:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dana Mison 2010-06-02 02:45:44 EDT
Description of problem:
In the html outputs, the dates in the revision history are right aligned, which IMHO makes them look mis-aligned since we read left to right.  

I think it looks okay for the author names to be right aligned since they are in the far right column.

The PDF is formatted as I would expect that the author names are left aligned as well.

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

How reproducible:
everytime :-)

Steps to Reproduce:
1. create a book with items in revision history
2. view revision history

Actual results:
revision history headers are right aligned with the exception of the first

Expected results:
revision history headers are left aligned with the possible exception of the last

Additional info:
edited common.css 

.revhistory td {
        border: none;
        border-top: 1px solid #fff;

could leave this out entirely and have it match the PDF
.revhistory tr td:last-child {

The table cells also have alignment set, which is being overridden by CSS, <td align="left">
Comment 1 Jeff Fearn 2010-06-10 00:03:40 EDT
Right aligned all cells in PDF and HTML.

Fixed in build: 1.6.3-0.t101
Comment 2 Ruediger Landmann 2010-07-11 23:51:43 EDT
Confirmed fixed in 2.1

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