After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 674183 - gnome shell activities overview should show full names on mouse hover
gnome shell activities overview should show full names on mouse hover
Status: RESOLVED DUPLICATE of bug 663725
Product: gnome-shell
Classification: Core
Component: overview
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-04-16 07:45 UTC by Romano Giannetti
Modified: 2014-11-07 19:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Romano Giannetti 2012-04-16 07:45:40 UTC 
The title says it all --- especially when choosing recent documents, if they start with the same say 12 or 14 letters, it's impossible to differentiate them (see attached shot).

When mouse is hovering an icon, the full name of the application/document should be shown.

See for example:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/968213/+attachment/2960346/+files/common_start_name.jpg
Comment 1 Felipe Erias Morandeira 2012-04-16 09:11:14 UTC 
Maybe a solution would be to allow document names to use more than one line of text, rather than having the user hover on each document and remember their titles.
Comment 2 Romano Giannetti 2012-04-16 10:18:43 UTC 
Yes --- that would be ok, too. Unless the name is very long... 
Probably the two things makes sense; use all the lines needed when hovering (even if the text goes over the icon underneath) and having more than one line as a default space.
Comment 3 Florian Müllner 2012-04-16 10:54:13 UTC 
See bug 663725 for making labels wrap instead of ellipsize.
Comment 4 Florian Müllner 2014-11-07 19:15:16 UTC 
(In reply to comment #3)
> See bug 663725 for making labels wrap instead of ellipsize.

Marking as duplicate now - the bug is clearly about the same issue, and the approach suggested in this bug shows up in the discussion there as well.

*** This bug has been marked as a duplicate of bug 663725 ***