Bug 1097060 - UI should truncate long host names while listing under 'Content Host'
Summary: UI should truncate long host names while listing under 'Content Host'
Keywords:
Status: CLOSED DUPLICATE of bug 1019773
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-13 05:54 UTC by Sachin Ghai
Modified: 2014-06-25 14:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-25 14:18:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
long host name starting with `shost..` overlaps with other fields (38.04 KB, image/png)
2014-05-13 05:54 UTC, Sachin Ghai 		no flags Details
View All

Description Sachin Ghai 2014-05-13 05:54:43 UTC 
Created attachment 894993 [details]
long host name starting with `shost..` overlaps with other fields

Description of problem:
Updated a content Host name with long name. It was updated successfully, however while displaying under content host, the name is overlapping other fields.

Version-Release number of selected component (if applicable):
Satellite 6 Beta Snap 4

Satellite-6.0.3-RHEL-6-20140508.1

How reproducible:
always

Steps to Reproduce:
1. Create a Host with long name
2.
3.

Actual results:
long host name overlaps other fields

Expected results:
UI should truncate host name.

Additional info:
Comment 2 Brad Buckingham 2014-05-20 12:28:22 UTC 
While this is an issue that needs to be addressed, I'd recommend that we work on it in a future release (e.g. 6.0.4). The likelihood of users creating host names that are that long is low.  In addition, it would be ideal if we could implement a generic solution to handle any attribute value that exceeds the width of the column.
Comment 3 Walden Raines 2014-06-25 14:18:38 UTC 

*** This bug has been marked as a duplicate of bug 1019773 ***
Note You need to log in before you can comment on or make changes to this bug.