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 687682 - Scroll bar visible in chat notification banners (when not expanded)
Scroll bar visible in chat notification banners (when not expanded)
Status: RESOLVED DUPLICATE of bug 692091
Product: gnome-shell
Classification: Core
Component: message-tray
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 691977 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-11-05 19:17 UTC by Volker Sobek (weld)
Modified: 2013-01-19 18:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Scrollbar in chat banner (34.18 KB, image/png)
2012-11-05 19:18 UTC, Volker Sobek (weld)
Details

Description Volker Sobek (weld) 2012-11-05 19:17:41 UTC
See attached screenshot. You see this best when you get the first message (someone starts a new conversation with you). The more messages you get/write, the more the scroll bar moves downwards until it is no longer visible in the banner.
Comment 1 Volker Sobek (weld) 2012-11-05 19:18:20 UTC
Created attachment 228180 [details]
Scrollbar in chat banner
Comment 2 Giovanni Campagna 2012-11-24 02:53:03 UTC
This is kind of weird actually: the scroll area is added on the second row, but it gets allocated on the same line as the banner.
Comment 3 Giovanni Campagna 2013-01-17 21:36:48 UTC
*** Bug 691977 has been marked as a duplicate of this bug. ***
Comment 4 Giovanni Campagna 2013-01-19 18:45:48 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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