Bug 773062 - Long names on Roles page not showing ellipsis properly FF3.6
Summary: Long names on Roles page not showing ellipsis properly FF3.6
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-10 19:52 UTC by Eric Helms
Modified: 2018-08-30 21:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-03 11:09:03 UTC
Target Upstream Version:


Attachments (Terms of Use)
screenshot-chrome20 (52.30 KB, image/png)
2012-07-13 17:42 UTC, Jeff Weiss
no flags Details

Description Eric Helms 2012-01-10 19:52:16 UTC
Description of problem:
On Firefox 3.6, when navigating elements on the roles page, long names are cut off and not shown as having an ellipsis.

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


How reproducible:


Steps to Reproduce:
1. Navigate to Roles page, create or choose pre-existing role
2. Create Global permission with long name (30+ characters)
3. View permission, and Click Edit Permission
  
Actual results:
Name of Permission in header is cut off with no ellipsis.

Expected results:
Expect to see partial name of permission followed by three dots.

Additional info:

Comment 1 Mike McCune 2012-01-26 19:39:07 UTC
mass move to CFSE product.

Comment 2 Jeff Weiss 2012-07-13 17:42:06 UTC
Created attachment 598128 [details]
screenshot-chrome20

Comment 3 Jeff Weiss 2012-07-13 17:42:49 UTC
Still not working in 1.1, chrome20:
Katello Version: 0.2.44-1.git.94.136cef9.el6_3

see screenshot - long names escape the left pane into the rest of the page.

Comment 5 Mike McCune 2013-08-16 18:14:43 UTC
getting rid of 6.0.0 version since that doesn't exist

Comment 6 Eric Helms 2013-10-03 11:09:03 UTC
Firefox 3.6 is no longer a supported browser.


Note You need to log in before you can comment on or make changes to this bug.