Bugzilla:Bug Layout Revision: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (→‎Wolf: Revising slightly misworded text.)
(adding deadline)
Line 2: Line 2:


preview of the work in progress is [https://landfill.bugzilla.org/prodpatches/show_bug.cgi?id=415 here]; note that logging in changes the appearance quite a bit.
preview of the work in progress is [https://landfill.bugzilla.org/prodpatches/show_bug.cgi?id=415 here]; note that logging in changes the appearance quite a bit.
{| style="background: lightgray; border: 1px solid blue"
| '''NOTE:''' Changes that don't have working patches by early evening PST Saturday December 23rd will not be included in the upgrade on Tuesday the 26th.
|}<br>


== Comments ==
== Comments ==

Revision as of 09:36, 22 December 2006

mconnor's proposal (which includes changes to the header) is here.

preview of the work in progress is here; note that logging in changes the appearance quite a bit.

NOTE: Changes that don't have working patches by early evening PST Saturday December 23rd will not be included in the upgrade on Tuesday the 26th.


Comments

(please include your rationale!)

Jesse

I like the wording changes and "edit" links. Those save space and make the page less cluttered.

I don't like the overall layout change. The three-column layout currently used at the top of bugs saves space, allowing me to see the CC list and the first few attachments without scrolling. Is there a good reason to switch to an entirely two-column layout?

beltzner

  • 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
  • Compress the header as in mconnor's mockup, the repetition of the bug name and number is distracting and confusing
  • The actions section takes up too much space and is too visually prominent. There doesn't need to be a "format for printing" button, we should just use a sensible print.css file. Clone bug and "XML" are seemingly low value, too. Instead I'd propose something like:
 Bug 415 - blah blah blah blah (edit)
 [view activity] [jump to latest comment]   (<-- small text)

Wolf

Agree with Jesse and Beltzner about the two vs three column layout stuff (and hiding the actions when searching.). Except for the header compression. I find the header appears better when not compressed. (and as far as I can see, there's no space actually being saved by those changes.) I think mirroring the actions line at the top and bottom is useful.

Removing the "Bug 415" (page title) portion might work on showbug, but on other pages, I don't think it does, since it provides useful information, which is only shown there. Plus the readdition of that value would likely end up being too wide with all the links on the same line. (See the activity log, etc). Also, why is preferences being changed to settings? Preferences seems to be more correct. 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.)