Bug 1205309 - Cropped labels and values in General subtabs
Summary: Cropped labels and values in General subtabs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ovirt-3.6.1
: ---
Assignee: Alexander Wels
QA Contact: Petr Matyáš
URL:
Whiteboard: ux
: 1139648 1139656 (view as bug list)
Depends On:
Blocks: 1067318 1255266
TreeView+ depends on / blocked
 
Reported: 2015-03-24 16:27 UTC by Greg Sheremeta
Modified: 2016-02-10 19:22 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-21 15:08:20 UTC
oVirt Team: UX
Embargoed:
sbonazzo: ovirt-3.6.z?
ylavi: planning_ack?
ecohen: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1149630 0 medium CLOSED Cropped labels and values in General subtabs 2021-02-22 00:41:40 UTC
oVirt gerrit 47334 0 None None None Never
oVirt gerrit 47484 0 None None None Never
oVirt gerrit 47598 0 None None None Never
oVirt gerrit 47913 0 None None None Never

Internal Links: 1149630

Description Greg Sheremeta 2015-03-24 16:27:55 UTC
Description of problem:
Cropped labels and values in General subtabs should have ellipsis applied ("..." suffix) and tooltip

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

How reproducible:
always

Steps to Reproduce:
1. shrink window size so info in a General subtab gets cropped
2. hover over a cropped value

Actual results:
no tooltip, no ellipsis

Expected results:
Labels and values should be suffixed with ... like in the grids.
A tooltip should show on those cropped values.

Additional info:
Related to / partial regression of Bug 1061379

Comment 1 Einav Cohen 2015-03-24 20:16:24 UTC
removed the "ellipsis" requirement from the BZ summary, as we would probably like to preserve the ability to copy (paste) the full label text, which would be impossible if ellipsis would be applied.
in the long term, we may need to think about a way to further improve this behavior. for now - let's preserve the functionality.

Comment 2 Einav Cohen 2015-08-09 07:09:29 UTC
*** Bug 1139648 has been marked as a duplicate of this bug. ***

Comment 3 Einav Cohen 2015-08-12 15:39:50 UTC
*** Bug 1139656 has been marked as a duplicate of this bug. ***

Comment 4 Red Hat Bugzilla Rules Engine 2015-10-19 10:50:07 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 Sandro Bonazzola 2015-10-26 12:29:10 UTC
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Comment 6 Sandro Bonazzola 2015-11-05 08:16:35 UTC
oVirt 3.6.0 has been released on November 4th, re-targeting to 3.6.1 since this bug has been marked as high severity

Comment 7 Einav Cohen 2015-11-19 13:45:44 UTC
QA:
- This was fixed by wrapping the labels and values in the General sub-tab; i.e. long labels/values will simply render over 2 lines (or more). 
- This is a general BZ. ** DO NOT REOPEN ** this BZ unless the bug is not fixed *in general*. *Specific* issues should be reported in separate, specific BZs. 

Thanks.

Comment 8 Petr Matyáš 2015-11-26 11:43:20 UTC
Verified on 3.6.0-22

Comment 9 Sandro Bonazzola 2015-12-16 12:22:19 UTC
Accordiing to target milestone and verification status this bug should be solved in oVirt 3.6.1. However, missing the target release field, this bug can't be moved to closed current release automatically.
Please check target_milestone and target_release and move to closed current release if included in oVirt <= 3.6.1.
Thanks.


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