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 787940 - improve legibility of the semi-transparent top bar
improve legibility of the semi-transparent top bar
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-09-20 12:31 UTC by Jakub Steiner
Modified: 2017-09-22 15:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
make top bar more legible (1.51 KB, patch)
2017-09-22 08:34 UTC, Jakub Steiner 		accepted-commit_now Details | Review

Description Jakub Steiner 2017-09-20 12:31:35 UTC 
This is a short term fix for the usability issues introduced with the semi-opaque top bar that landed for 3.26.

To increase legibility we should 

- offset the dropshadow 1px in Y
- increase the overall opacity of the top bar
Comment 1 Florian Müllner 2017-09-20 16:22:56 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 783913 ***
Comment 2 Jakub Steiner 2017-09-22 08:34:26 UTC 
Created attachment 360245 [details] [review]
make top bar more legible
Comment 3 Jakub Steiner 2017-09-22 08:35:38 UTC 
This isn't a solid future proof fix as bug 783913 is trying to address, more like a hotfix for the current really bad situation.
Comment 4 Florian Müllner 2017-09-22 11:30:54 UTC 
Review of attachment 360245 [details] [review]:

(In reply to Jakub Steiner from comment #3)
> This isn't a solid future proof fix as bug 783913 is trying to address

Is that really that far off from landing though? I had the impression that it was mostly about tiny details that could be figured out in time for 3.26.1. Anyway, there's no reason to not go ahead with this now, so feel free to push ...