Closed
Bug 107379
Opened 23 years ago
Closed 22 years ago
Inconsistent table grouping
Categories
(Bugzilla :: Query/Bug List, defect, P3)
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
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.16
Comment 3•23 years ago
|
||
CCing myk, who is templatising buglist.cgi. Gerv
Comment 4•23 years ago
|
||
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.
Comment 5•23 years ago
|
||
Here is a test case by which the fixing of this bug can be verified: http://bugzilla.mozilla.org/buglist.cgi?email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=1000&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=2001&cmdtype=doit&namedcmd=2.12&newqueryname=&order=Reuse+same+sort+as+last+time
Comment 6•23 years ago
|
||
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
Comment 7•22 years ago
|
||
This bug has been fixed by the check-in on bug 103778.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 9•22 years ago
|
||
fixing incorrect milestones on fixed bugs.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.16
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•