-
Notifications
You must be signed in to change notification settings - Fork 19
Transparent top panel when in opaque state creates some mind boggling use case #173
Comments
Oh, that is why I've never tested this situation 😞
indeed it is possible, moreover a ticket has been already opened from a guy who thought it was a bug. So maybe, transparent panel when everything goes solid is not so intuitive. I think transparent top panel on maximized window is kind of a living thing 😄, it looks good or bad depending on the wallpaper and the display quality, so if we keep it, we should accept we won't have total control of it. To me it is fine to give a test to fully opaque again, also because we changed titlebar/menubar relationship last week and so the effect could be nice. |
@didrocks - What I can't understand. how come some windows goes under the top-panel? |
@Paz-it you need a dual monitor setup with one monitor above the other and the top panel in the display at the bottom, then when you move a windows to the display at the top, the window goes under the top panel |
(that, or on a single monitor setup: having a window popping up, like dialogs, with fixed height higher than monitor size, or forcing it with Super + mouse click if you really want hurt yourself ;)) |
Transparent top panel on maximized windows might cause some misundersanding for the user. See #173
Transparent top panel on maximized windows might cause some misundersanding for the user. See #173
@didrocks just a question which came up in a different issue: did this also happen (hard to reproduce now) if you disabled the desktop in tweaks? |
Yes, this has nothing to do with desktop icons. |
Transparent top panel looked so nice 😢 |
Is there a way (like in CSS) to "fake" a transparent background? Like put the desktop-background-image as a background behind the transparent bar when maximized? Needs to be positioned and cropped as a second layer behind the bar... but maybe possible? And everything behind the bar will be hidden and still look like transparent. |
@Feichtmeier: please reread the thread on the forum, this isn't limited to multi-monitors only, there are cases with some screen resolutions this happens on a single monitor case with transient dialogs. |
@Luxamman: this is an interesting idea, maybe possible with some pseudo-elements. The benefit is that in that case, we'll have a consistent background color, while still have some transparency. |
Yesterday I tried with a background-image to mimic blur effect on panel, but no result yet. It might be due to my lack of svg skills however 😄 , I'll try again later |
OK, tried again and get support from IRC #gnome-shell: I'm able to make a nice and useless transparent background image, but blurred background is not supported. Now, what about that pseudo-elements? 😄 |
I'm not even sure this is supported by the Shell, but thinking from my small css knownledge, some people uses :before and :after pseudo elements, and then reposition it to fit the main element position and size, behind the main element. There, we can maybe add a background color… |
What puzzles me is how to add the actual background wallpaper, but I'll look into it. One thing we could do is use the same color we would have had with transparency + default ubuntu wallpaper. Just thinking out loud though, I know it wouldn't be the same 😞 |
It doesn't seem that bad to me if we can pick the average color of the wallpaper with transparency and use that. At least, whatever is the wallpaper, you are sure the text is readabale. |
Is a gradient possible? This - unfortunately - isn't solving the main problem here, but maybe an idea for max window mode. And I also don't see the problem resolved in vanilla...? Quick mockup - brightness adjustment will be a b*** here: |
I asked the author of the awesome blyr extension for an idea on how to bypass our issue with a blur and here is his answer: |
I made some tests, but gradient seems not supported (same gradient works in gtk-communitheme, but not in panel). Solid color, like a mix between Canonical's colors, is possible though |
How about using an .svg for the panel and condition it to change color acording the wallpaper but only when windows are maximize? It was possible in Unity. |
pity that we are technically limited - dark aubergine for the top and just slightly brighter for the dock could look good - did you already try that @clobrano? |
That's my last try on weither this is really such a problematic situation (I am searching parallel for solutions btw, so please don't get the impression I try to block some greater decision ;O) or not: I want to point out once again, that we are using gnome shell here. Maybe gnome shell has some performance issues but there is really one thing that does the shell right and that is the dash/activities/workspace overview. And this is if you want to use two applications beneath each other: Vanilla gnome shell (gnome-session) uses the transparent top panel with unmaximized windows, too. So those situations would also occur in gnome-session. |
@Feichtmeier I'm with you, like said. Rather solving the "grey wall" problem, than a gnome vanilla problem... |
Not with Gnome shell, but I don't understand how this would solve the problem.
😄 however you might still do the other way. It would be awesome if mutter was able to avoid headerbars to stay under the panel (maybe moving them by some pixels) :( @didrocks you think the above ^ is possible? Or Mutter is the wrong actor here? |
It's certainly better than it was last week 😄 |
Well, back to all black^^ |
@Luxamman |
oupsss, sorry @clobrano, didn't see your ping. No, this isn't something that Mutter is able to handle AFAIK (and yes, it's the correct actor). I doubt as well upstream would change this behavior as it's not a problem for them (black panel) @Feichtmeier: sorry, what do you mean by jet shell?
Note that it's not "unmaximized windows" which goes for transparent Shell, the algorightm is "when no windows is in next to the panel (some pixels or touching it). We extended that in the ubuntu session by "when no windows is next to the panel or dock". |
@didrocks the color of the opaque panel and dock which is in master now to solve both that problems mentioned in this issue and the grey wall of doom |
After a |
I agree, but perhaps I can push the fact that controls under a panel are not usable anymore 😃 I'll have a look at mutter, but I might need some help (on IRC) to set it correctly. Tried some times before and got some problems... |
All these situations can also occur when not maxed and not only in communitheme session but also ubuntu (dock and panel) and gnome session (panel). So how much is this an issue too ? |
I don't think when the button aren't usable due to controls being under an opaque panel is an issue personnally: you don't see it, you can't click on it. That makes sense to me :) |
Closing this since the panel is not transparent anymore in this state |
I find that there can be some cognitive issues as the top panel isn't fully opaque when an application touches it.
Here are 3 use cases where I understand why this happens, but I'm afraid some users won't. Note that I'm with the default bionic wallpapers, and an application is maximized, so the panel is at max opacity in the theme.
Here is the case with a window in the background, under the panel. Especially when you focus other apps, you have that weird top bar mix.
With a window in foreground, another effect is puzzling: you see the window control, and some parts are thus a little bit more opaque (as you have the panel on front), instead of obfuscating it. I'm afraid that lead to people hovering and clicking it, while triggering another action (like the panel date, or the system wifi-sound-session menu)
It's even more visible when there is a suggested action in the headerbar.
It's not a strong case that the panel should be fully opaque, but I would like that we think of those issues. Is it only me who finds it mind boggling?
Note that I have 2 monitors (one on top of the other), and this is why I can easily (without Super + press) end up in that situation, the panel being on top of the bottom monitor.
The text was updated successfully, but these errors were encountered: