Closed Bug 107379 Opened 23 years ago Closed 22 years ago

Inconsistent table grouping

Categories

(Bugzilla :: Query/Bug List, defect, P3)

2.15
defect

Tracking

()

VERIFIED FIXED
Bugzilla 2.16

People

(Reporter: xyzzy, Assigned: endico)

References

()

Details

When displaying large (>199 bugs) bug lists, Bugzilla groups 199 bugs into 
the first table, and subsequently groups 200 bugs at a time.

This is pretty minor, but I do notice it, and can fix it.  I also want to change 
the 200 to 100 if there are no objections.  It seems a little more intuitive, 
and since I'm on a slow connection, it would give me feedback sooner.  

Change:

1240         $count++;
1241         if ($count % 200 == 0) {
1242             # Too big tables take too much browser memory...
1243             pnl "</TABLE>$tablestart";
1244         }

to:

         if (($count % 100 == 0) && ($count > 0)) {
             # Too big tables take too much browser memory...
             pnl "</TABLE>$tablestart";
         }
         $count++;

or:

         $count++;
         if (($count % 100 == 1) && ($count > 1)) {
             # Too big tables take too much browser memory...
             pnl "</TABLE>$tablestart";
         }

Yay, I knew I'd contribute code someday!  :P
Added patch keyword to get CVS love.
Keywords: patch
Needs review first, though...
Keywords: review
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.16
CCing myk, who is templatising buglist.cgi.

Gerv
Depends on: 103778
Thanks for the contribution!  I have incorporated this code into the templatized
version of buglist.cgi (bug 103778), including the reduction from 200 to 100
bugs per table.
We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
This bug has been fixed by the check-in on bug 103778.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
verified on tip
Status: RESOLVED → VERIFIED
fixing incorrect milestones on fixed bugs.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.16
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.