Bug 1199725 - Cropped column-header text should have ellipsis applied ("..." suffix)
Summary: Cropped column-header text should have ellipsis applied ("..." suffix)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Greg Sheremeta
QA Contact: Pavel Stehlik
URL:
Whiteboard:
: 1271207 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-07 13:45 UTC by Einav Cohen
Modified: 2022-05-16 07:47 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-08 16:54:43 UTC
oVirt Team: UX
Embargoed:
sbonazzo: ovirt-4.2-


Attachments (Terms of Use)
screen-shot: Cropped text, grid header vs. grid body (118.36 KB, image/png)
2015-03-07 13:45 UTC, Einav Cohen
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46045 0 None None None 2022-05-16 07:47:08 UTC

Description Einav Cohen 2015-03-07 13:45:56 UTC
Created attachment 999144 [details]
screen-shot: Cropped text, grid header vs. grid body

Currently, when a column header text is cropped, there is not ellipsis ("..." suffix) applied/activated on the text - the text is simply cropped. 
Cropped column header text should have ellipsis activated on it, just like we have for text in cells within the grid's body. 

See attached screen-shot for problem demonstration.

Comment 1 Red Hat Bugzilla Rules Engine 2015-10-19 10:55:58 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 2 Sandro Bonazzola 2015-10-26 12:40:52 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 3 Einav Cohen 2015-11-03 18:21:43 UTC
(In reply to Sandro Bonazzola from comment #2)
> 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

@Greg - is it good material for you to work on with Scott? If so - let's keep it on 3.6.z, otherwise - let's push for 4.0.0.

Comment 4 Greg Sheremeta 2015-12-09 04:24:25 UTC
4.0 it is

Comment 5 Red Hat Bugzilla Rules Engine 2015-12-09 04:24:30 UTC
This bug is marked for z-stream, yet the milestone is for a major version, therefore the milestone has been reset.
Please set the correct milestone or drop the z stream flag.

Comment 6 Einav Cohen 2016-01-12 14:05:50 UTC
*** Bug 1271207 has been marked as a duplicate of this bug. ***

Comment 8 Yaniv Kaul 2016-03-10 16:11:47 UTC
(In reply to Greg Sheremeta from comment #4)
> 4.0 it is

No idea why it's high severity. Any updates on this item? Is it going into 4.0?

Comment 9 Greg Sheremeta 2016-03-10 16:40:05 UTC
No updates from me. You'll want to ask Oved about what goes into 4.0 :)

Comment 10 Oved Ourfali 2016-03-21 11:17:06 UTC
Actually we recently found that this mechanism can cause issues, while examining the memory leak.
Greg - am I correct?

Comment 11 Greg Sheremeta 2016-03-21 13:43:26 UTC
Not quite. The method we use to detect truncated text is just really slow. But it does not leak.

Comment 12 Sandro Bonazzola 2016-05-02 09:58:35 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 13 Greg Sheremeta 2016-05-13 20:44:57 UTC
This won't make 4.0.

Comment 14 Yaniv Kaul 2017-09-04 10:52:43 UTC
Any news in the new 4.2 UI?

Comment 15 Oved Ourfali 2017-09-04 11:52:24 UTC
(In reply to Yaniv Kaul from comment #14)
> Any news in the new 4.2 UI?

We didn't handle that yet.

Comment 16 Greg Sheremeta 2017-09-05 14:42:18 UTC
(In reply to Oved Ourfali from comment #15)
> (In reply to Yaniv Kaul from comment #14)
> > Any news in the new 4.2 UI?
> 
> We didn't handle that yet.

Right. If you're curious, we didn't swap out the grid technology in 4.2. It's still the same GWT grid -- just styled with PatternFly CSS instead of our old (GWT-based) CSS.

Comment 17 Greg Sheremeta 2018-01-08 16:54:43 UTC
Closing due to lack of capacity.


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