Red Hat Bugzilla – Bug 1025728
Artificial line wrapping of bugs wastes browser real estate
Last modified: 2013-11-26 00:30:55 EST
Description of problem:
In many of the bugs I have to deal with, people paste in log messages and other blocks of pre-formatted text. Unfortunately the bugzilla CSS is causing the text to line wrapped at 600px, by using a constrained dimension for comment text blocks. My browser window meanwhile is 1980px wide, and has plenty of space to view the text from bugs without artificial line wrapping.
This rather harms the usability of bugzilla viewing comments
If I wanted text wrapped at 600px, then I could keep my browser window at such small sizes. I intentionally have a large browser window so I can see line longs without artifical wrapping, but bugzilla CSS prevents that.
This doesn't seem to be Red Hat specific - switching to the 'Classic' CSS style, I see the same thing. So I think Red Hat CSS would need to override whatever upstream CSS rule does this fixed width.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open https://bugzilla.redhat.com/show_bug.cgi?id=1005570
2. Look at text in comment #3
CSS causes log lines to be line wrapped, totally mangling the comment, making it unreadable.
Comment is allowed to fill entire browser window horizontal real estate.
Created attachment 818260 [details]
Broken formatting caused by BZ CSS constraining comment width
Created attachment 818261 [details]
Good formatting when CSS is disabled, allowing comment to fill browser window width
Comments are wrapped by default. You can change the default behaviour by changing the "Wrap comments by default" value in your preference, or temporary by clicking the 'Unwrap comments' link to the right of the topmost comment.
When doing this, comment 3 expands as wide as my browser allows (except for the space required to show the links on the right of the top most comment)
 This is the bug description by default, unless you sort your comments as newest first.
*** This bug has been marked as a duplicate of bug 965911 ***