Bug 604032 - Add more space between resource type and name in resource tables
Summary: Add more space between resource type and name in resource tables
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI   
(Show other bugs)
Version: 3.0.0
Hardware: All
OS: Linux
low vote
Target Milestone: ---
: ---
Assignee: Lukas Krejci
QA Contact: Corey Welton
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-15 08:42 UTC by Lukas Krejci
Modified: 2010-08-12 16:47 UTC (History)
0 users

Fixed In Version: 2.4
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-12 16:47:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
type and name close together (7.50 KB, image/png)
2010-06-15 08:42 UTC, Lukas Krejci
no flags Details

Description Lukas Krejci 2010-06-15 08:42:17 UTC
Created attachment 424076 [details]
type and name close together

Description of problem:

The "Resource" column in various places in UI contains a resource type name in  italics followed by the resource name (if it is a link, it is in bold, otherwise normal).

The type and name are separated using only a single space making them look very close together.

More space should be added between them to more clearly separate the type from the name.

How reproducible:

Steps to Reproduce:
1. Look at dashboard portlets containing resource tables or look at the search results page or anywhere, there is a tabular list of resources.
2. The "Resource" column should contain type and name (for non-singleton resources)
Actual results:
The type and name are visually too close together.

Expected results:
More visual separation would be good.

Comment 1 Lukas Krejci 2010-07-13 10:55:39 UTC
Fixed in commit 57a0a3942317494496b730708279fae1dbc45347

Comment 2 Corey Welton 2010-07-15 12:22:01 UTC
QA Verified...

Comment 3 Corey Welton 2010-08-12 16:47:59 UTC
Mass-closure of verified bugs against JON.

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