Closed Bug 27420 Opened 23 years ago Closed 22 years ago

Component field should have COLSPAN in long_list.cgi

Categories

(Bugzilla :: User Interface, enhancement, P4)

x86
Linux
enhancement

Tracking

()

RESOLVED FIXED
Bugzilla 2.16

People

(Reporter: randall.whitman, Assigned: myk)

Details

Attachments

(1 file)

We find that the Component field of the long_list table output very
frequently wraps onto more than one line, when it appears that there
is plenty of room to fit it on one line.  In my understanding,
Target Milestone is a short field (not longer than Component),
so it should work to give COLSPAN=2 to the table cells for both
Component and Target Milestone.

diff -r1.12 long_list.cgi
104c104
<         print "<TR><TD><B>Component:</B> $component\n";
---
>         print "<TR><TD COLSPAN=2><B>Component:</B> $component\n";
106c106
<             print "<TD><B>Target milestone:</B>$target_milestone\n";
---
>             print "<TD COLSPAN=2><B>Target milestone:</B>$target_milestone\n";
tara@tequilarista.org is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)
Assignee: terry → tara
Adding default QA contact to all open Webtools/Bugzilla bugs lacking one.
Sorry for the spam.
QA Contact: matty
Target Milestone: --- → Bugzilla 2.16
Keywords: patch, review
Priority: P3 → P4
-> Bugzilla product, User Interface component, reassigning.
Assignee: tara → myk
Component: Bugzilla → User Interface
Product: Webtools → Bugzilla
Version: other → unspecified
myk: do we want to do this?

Gerv
I can't believe a patch like this has been sitting for so long.  This is
reasonable, yes we want it.
Comment on attachment 52902 [details] [diff] [review]
patch w/colspan=2 plus capitalization and spacing corrections

r= justdave
no 2nd review needed
Attachment #52902 - Flags: review+
Checked-in.  Resolving fixed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.