Currently when a comment has been added to an object, webadmin portal displays a yellow paper sheet icon in the "Comment" column.
Customer is requesting that the content of the comment is displayed instead of the yellow icon.
If the comment is longer than the width of the column and consequently the full content of the comment can not be displayed, then as much content as possible should be displayed followed by "..." to indicate that the comment is longer than displayed and that user should hover the mouse over it to be presented with the full content of the comment.
@Alona: Is the LabelWithTextOverflow that you have introduced in http://gerrit.ovirt.org/#/c/29125/ appropriate for usage in the grids as well (i.e. for text values for which the current column width is not enough in order to be fully displayed)? or will that require a completely different infrastructure?
The tables' columns already implement mechanism that shows tooltip if the content overflows. So you just need the "...". It is very easy to achieve this by adding "text-overflow: ellipsis" to the style of the column's text.
I"ve sent a patch that doing it- http://gerrit.ovirt.org/#/c/31384/
Now all the comment columns can use regular TextColumnWithTooltip and CommentColumn can be removed.
(In reply to Alona Kaplan from comment #3)
> The tables' columns already implement mechanism that shows tooltip if the
> content overflows. So you just need the "...". It is very easy to achieve
> this by adding "text-overflow: ellipsis" to the style of the column's text.
> I"ve sent a patch that doing it- http://gerrit.ovirt.org/#/c/31384/
> Now all the comment columns can use regular TextColumnWithTooltip and
> CommentColumn can be removed.
excellent - I thought that the tool-tip mechanism existed only for the column headers, not for the column "body"s.
many thanks, Alona - much appreciated!
Einav, what if some people like the bubble? Since we don't have a way to set a preference in the application, I worry this could upset some users.
Original request was not to remove the bubble, just to display as much as possible of the content in the column itself, followed by "..." if all the content does not fit in the column.
Users should still be able to hover over it to get the yellow bubble.
(In reply to Greg Sheremeta from comment #5)
> Einav, what if some people like the bubble? Since we don't have a way to set
> a preference in the application, I worry this could upset some users.
as Julio mentioned: we are just replacing the yellow "postit" icon with the content of the comment; now that we have the "text-overflow: ellipsis" in place, we are still expected to display a tool-tip in case the comment cannot be fully displayed in its currently-allocated space (based on the column's width).
for users that are worried about real-estate: the comment-column default width should be something wider than it is right now, however users to which the comment's content wouldn't really matter will always be able to reduce the column width to something very small (like it is today).
users that do care about the comment's content may obviously need to reduce the width of other columns in favor of the comment's column width.
moreover, once bug 957600 will be resolved, the user will be able to hide some columns that are not important for him, in favor of more real-estate to the comment column [or any other column(s) that he finds important].
Greg - I hope this answers your question; if not - feel free to 'needinfo' me again.
there is a chance that the term "bubble" was used here to describe two things: (1) the yellow "postit" icon [Greg] (2) the tool-tip displayed when hovering on the icon today [Julio]
(I might have misunderstood, don't know)
let's use the "'postit' icon" and "tool-tip" terms, in order to avoid confusion. thanks.
Yeah, I was using "bubble" to mean "post-it". Sorry about that.
No need to reply to my question, though. If people want to, they can shrink the comment column very small. Same effect as the post-it icon.
Created attachment 995390 [details]
new comment column
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.