Changes

Jump to: navigation, search

Bugzilla:Bug Layout Revision

32 bytes added, 15:19, 28 December 2006
m
no edit summary
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.
=== LpSolit ===
Now I strongly disagree to have the keywords, URL and status whiteboard fields at the very top. This looks wrong to me. More important is the block with the assignee + target milestone + severity, and should be moved higher in the page. The status and resolution should be combined with this block.
 
=== Dolske ===
* 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 -> ???.
=== LpSolit ===
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.
 
''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.
Note on bug 415 that I reassigned the bug to timeless, who has no real name on b.m.o, and now the assignee field is left blank. If the user has no realname, then his email address should be displayed.
Now I strongly disagree to have the keywords, URL and status whiteboard fields at the very top. This looks wrong to me. More important is the block with Nit: please remove the assignee + target milestone + severity, and should be moved higher now useless colspan=3 in the page. The status and resolution should be combined with this block. Ancestor, about right table as the dependency lists: it indeed tries to use as much place as possible, but will wrap have been moved 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 oftenleft.
* Putting page specific info (the bug title) into the top header seems like a unusual design, so the location would seem unexpected. Most sites have a relatively static header that one learns to ignore.
* 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 ===
27
edits

Navigation menu