Bug 1003975 - The Content Repository tab within the Admin console does not display the full text of "Name" and "RunTime Name", as it did in EAP 6.0
Summary: The Content Repository tab within the Admin console does not display the full...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER3
: EAP 6.2.0
Assignee: Heiko Braun
QA Contact: Michal Karm Babacek
Russell Dickenson
URL:
Whiteboard:
: 1003971 (view as bug list)
Depends On:
Blocks: 1003533 1044104
TreeView+ depends on / blocked
 
Reported: 2013-09-03 15:23 UTC by Travis Rogers
Modified: 2019-05-20 11:05 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
: 1044104 (view as bug list)
Environment:
Last Closed: 2013-12-15 16:49:13 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HAL-163 0 Major Resolved The Content Repository tab within the Admin console does not display the full text of "Name" and "RunTime Name" 2015-05-07 10:44:13 UTC

Description Travis Rogers 2013-09-03 15:23:52 UTC 
In the "Content Repository" tab, "Name" and "RunTime Name" do not display the full text of the names, as in 6.0.  The names are trimmed and elipses are added for display purposes, but there isn't a facility to show the full name.  Not even a "mouse over" to display the full text in a highlight or something to that effect.
Comment 1 JBoss JIRA Server 2013-09-10 14:45:38 UTC 
Harald Pehl <hpehl> updated the status of jira HAL-163 to Resolved
Comment 2 JBoss JIRA Server 2013-09-10 14:45:38 UTC 
Harald Pehl <hpehl> made a comment on jira HAL-163

The fulltext is visible as tooltip on mouseover
Comment 3 Heiko Braun 2013-09-16 08:19:07 UTC 
*** Bug 1003971 has been marked as a duplicate of this bug. ***
Comment 4 Michal Karm Babacek 2013-09-27 10:39:34 UTC 
Looks good with my Firefox 23.0.1. Verified.
Note You need to log in before you can comment on or make changes to this bug.