27
edits
Bugzilla:Bug Layout Revision: Difference between revisions
Bugzilla:Bug Layout Revision (view source)
Revision as of 15:07, 28 December 2006
, 28 December 2006no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 20: | Line 20: | ||
* Agree with Jesse, 3 columns allows for more information density on a page and will actually make it easier to visually scan each chunk/grouping | * Agree with Jesse, 3 columns allows for more information density on a page and will actually make it easier to visually scan each chunk/grouping | ||
* When no search results are available, just hide that row since it adds no valuable information | * When no search results are available, just hide that row since it adds no valuable information | ||
=== Peter === | |||
I very much like the 2 column layout. The old 3-column layout only works when running with the browser window maximized (horizontally). I almost never do that and so that caused a lot of very annoying horizontal scolling. The proposed 2 column layout scales much better in width. | |||
== Comments before bmo upgrade, that are solved now == | == Comments before bmo upgrade, that are solved now == | ||
| Line 33: | Line 39: | ||
[view activity] [jump to latest comment] (<-- small text) | [view activity] [jump to latest comment] (<-- small text) | ||
=== Ancestor === | |||
The dependency list tries to put as many entries in one line as it can. This becomes a problem when there are plenty of entries, because it pushes the right-hand column too far to the right. [https://landfill.bugzilla.org/prodpatches/show_bug.cgi?id=4728 see here for example]. | |||
=== LpSolit === | |||
''I know that but I feel it would be better to wrap the dependency list earlier so that the columns aren't so far apart from each other with a huge white space between them. - Ancestor'' | |||
Nit: please remove the now useless colspan=3 in the right table as the dependency lists have been moved to the left. | |||
| Line 46: | Line 60: | ||
I'm not sure print view is served well by being just print.css fixed (as the page says, its a full text bug list, not really just a css change. Agree about XML, not sure what the purpose for it is, not that it bothers me being there, either. Clone Bug might be of value, though, since it didn't work in bmo before. (Just having two links to me, suggests either over pruning, or that that line should be elsewhere.) | I'm not sure print view is served well by being just print.css fixed (as the page says, its a full text bug list, not really just a css change. Agree about XML, not sure what the purpose for it is, not that it bothers me being there, either. Clone Bug might be of value, though, since it didn't work in bmo before. (Just having two links to me, suggests either over pruning, or that that line should be elsewhere.) | ||
=== LpSolit === | === LpSolit === | ||
| Line 62: | Line 74: | ||
Ancestor, about the dependency lists: it indeed tries to use as much place as possible, but will wrap to avoid the user to scroll horizontally, so this is fine and exactly what we want. If your screen is narrower, it will wrap more often. | Ancestor, about the dependency lists: it indeed tries to use as much place as possible, but will wrap to avoid the user to scroll horizontally, so this is fine and exactly what we want. If your screen is narrower, it will wrap more often. | ||
=== Vlad === | === Vlad === | ||
| Line 76: | Line 84: | ||
* Status and Resolution have already been combined in the new version (now "Status: RESOLVED INVALID"). It might be worthwhile to combine a few other fields (ie, put them in the same row). For example, Hardware + OS -> Platform (System?). And perhaps Priority + Severity -> ???. | * Status and Resolution have already been combined in the new version (now "Status: RESOLVED INVALID"). It might be worthwhile to combine a few other fields (ie, put them in the same row). For example, Hardware + OS -> Platform (System?). And perhaps Priority + Severity -> ???. | ||
=== Napolj2 === | === Napolj2 === | ||