Bug 965911

Summary: Add a trigger to release comment width limit
Product: [Community] Bugzilla Reporter: Monson Shao <jshao>
Component: User InterfaceAssignee: Simon Green <sgreen>
Status: CLOSED CURRENTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: berrange, ccui, ebaak, jingwang, rjoost, rsteiger, teigland
Target Milestone: 4.4   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.4.0009 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1318165 (view as bug list) Environment:
Last Closed: 2013-10-04 00:46:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1318165    

Description Monson Shao 2013-05-22 02:29:34 UTC
Description of problem:

Now comment width is limited by

.bz_comment_text {
     width: 50em;
}

It will cause autowrap when comments exceed this and it is good for discussion. But for codes or calltrace, autowrap will make things hard to understand, we want them showed as original if possible.

Version-Release number of selected component (if applicable):
4.4

Actual results:
all comments are autowrap.

Expected results:
some way to disable autowrap

Additional info:

Comment 1 Simon Green 2013-05-26 23:39:44 UTC
*** Bug 966131 has been marked as a duplicate of this bug. ***

Comment 2 Simon Green 2013-05-26 23:44:22 UTC
We will add two things:

1) A preference on whether the default should be to wrap or not. The default will be to wrap. Since this would be what the majority of users would want.

2) A toggle option at the top of the comments (under 'Expand All Comments') so that this can be changed specifically for a single page load.

  -- simon

Comment 3 Simon Green 2013-07-23 23:59:40 UTC
*** Bug 605715 has been marked as a duplicate of this bug. ***

Comment 5 Simon Green 2013-10-04 00:46:38 UTC
This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.

  -- simon

Comment 6 Simon Green 2013-11-26 05:30:55 UTC
*** Bug 1025728 has been marked as a duplicate of this bug. ***