Bug 1254087 - Component field got truncated when component string is very long
Summary: Component field got truncated when component string is very long
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 4.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: 4.4
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-17 07:15 UTC by Rony Gong 🔥
Modified: 2018-12-09 06:29 UTC (History)
3 users (show)

Fixed In Version: 4.4.10045.3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-16 02:13:48 UTC
Embargoed:

Attachments (Terms of Use)
screen capture in 4.4.9039.1 (20.33 KB, image/png)
2015-08-17 07:15 UTC, Rony Gong 🔥 		no flags Details
View All

Description Rony Gong 🔥 2015-08-17 07:15:59 UTC 
Created attachment 1063646 [details]
screen capture in 4.4.9039.1

Description of problem:
Component field got truncated when component string is very long

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

How reproducible:
Always

Steps to Reproduce:
1.Create a rhel7 bug, then select component 'Red_Hat_Enterprise_Linux-Release_Notes-7-zh-TW', save
2.
3.

Actual results:
The component field value got truncated

Expected results:
not truncated, It is better show in 1 lines, but in 2 lines also acceptable.

Additional info:
check attachment
Comment 1 Jeff Fearn 🐞 2015-10-15 07:19:23 UTC 
Currently this wraps, but if you have a component with a name that fills up the widget then end of the widget is under the arrow widget making it hard to read.

This css should fix it:

.selectize-input .item {
  max-width: 24em;
}
Comment 2 Rony Gong 🔥 2015-10-28 07:49:17 UTC 
Tested on 
QA environment(bzperfweb01.app.qa) with version(4.4.10043-2, DB: psql)
Result: Pass
Comment 3 Matt Tyson 🤬 2015-12-16 02:13:48 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.
Note You need to log in before you can comment on or make changes to this bug.