Bug 965911 - Add a trigger to release comment width limit
Summary: Add a trigger to release comment width limit
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: User Interface
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 4.4
Assignee: Simon Green
QA Contact: tools-bugs
URL:
Whiteboard:
: 605715 966131 1025728 (view as bug list)
Depends On:
Blocks: 1318165
TreeView+ depends on / blocked
 
Reported: 2013-05-22 02:29 UTC by Monson Shao
Modified: 2018-12-09 06:29 UTC (History)
7 users (show)

Fixed In Version: 4.4.0009
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1318165 (view as bug list)
Environment:
Last Closed: 2013-10-04 00:46:38 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 823423 0 unspecified CLOSED the right side text fields and the long link in comments are out of the normal frame. 2021-02-22 00:41:40 UTC

Internal Links: 823423

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. ***
Note You need to log in before you can comment on or make changes to this bug.