Closed Bug 38624 Opened 26 years ago Closed 25 years ago

"New value" column smaller than "old value" column

Categories

(Bugzilla :: Bugzilla-General, defect, P3)

Other
Other
defect

Tracking

()

VERIFIED FIXED
Bugzilla 2.12

People

(Reporter: jruderman, Assigned: Chris.Yeh)

Details

(Whiteboard: 2.12)

The "new value" column is smaller than the old value column, making it difficult to figure out exactly what was changed in a field like cc. What |Old Value |New Value ---------------------------------------------------------------------------- CC|Antti.Nayha@oulu.fi,Crysgem@|Antti.Nayha@oulu.fi,Crysgem |crosswinds.net,bissiri@eecs.|@crosswinds.net,bissiri@eec |umich.edu,davidr8@home.com,d|s.umich.edu,davidr8@home.co |baron@fas.harvard.edu,janc@n|m,dbaron@fas.harvard.edu,ja |etscape.com,katakai@japan.su|nc@netscape.com,katakai@jap |n.com,rich.burridge@Sun.COM,|an.sun.com,rich.burridge@Su |tajima@eng.sun.com |n.COM,tajima@eng.sun.com,va | |rga@utcru.sk
Assignee: tara → cyeh
Whiteboard: 2.12
i'll look at this for 2.12
added extra char width in FormatTriple so that old/new are the same size. thanks for the excellent bug report, it was very easy to find.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
When is this bugfix going to appear in bugzilla.mozilla.org? Two months after it was marked fixed, I'm still getting skewed columns in my notifications.
ccing endico@mozilla.org, owner responsible for bugzilla.mozilla.org Bugzilla installation. Note: checkins to the trunk do not get immediately reflected to bugzilla.mozilla.org.
I plan to not update bugzilla.mozilla.org to the tip until after the insanity is over with 6.0.
Sorry for the spam, but I needed to be able to query for all of these correctly.
Target Milestone: --- → Bugzilla 2.12
VERIF - 27 chars in each. (The file is processmail.) Gerv
Status: RESOLVED → VERIFIED
Moving closed bugs to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.