Issue metadata
Sign in to add a comment
|
GTK+ theme ignored in omnibar in the new interface
Reported by
virus.fl...@gmail.com,
Jul 12
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/68.0.3440.42 Chrome/68.0.3440.42 Safari/537.36 Steps to reproduce the problem: I have a dark GTK+ theme (Adwaita Dark). What is the expected behavior? What went wrong? Screenshot 1 shows Chromium's omnibar in Chromium 68 - it follows system colors - dark background as in the GTK+ theme. Screenshot 2 shows new UI - it does not follow system colors and destroys my eyes by white background. Did this work before? N/A Chrome version: 69.0.3486.0 Channel: dev OS Version: Flash Version:
,
Jul 16
Able to reproduce the issue on reported chromium version 69.0.3486.0 also on latest chrome 69.0.3494.0 using Mac 10.13.5, Ubuntu 17.10 and Windows 10. Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. Thanks!
,
Jul 16
I don't remember the status bar to have white background on dark GTK+ themes in chromium version 60... Why is it a non-regression? Is it a design solution? A very bad one, if yes, because it hurts eyes. It's color is OK in version 68, but is not in 69.
,
Jul 16
To be more exact, it's probably not a regression for the new UI, but as the new UI will become default, it's a regression for user experience.
,
Jul 17
,
Jul 17
+tommicli is the omnibox no longer using the native theme colors? I'm using the same theme as the OP and I'm seeing the same regression.
,
Jul 18
Hey Joel / Alan, What's our plan for respecting native theme colors in MD Refresh? Tommy
,
Aug 28
Ping. It's now in Beta, and it's really awful
,
Aug 28
One more issue: now the contast between the active tab and others is very low, lower than before, it's very hard to find which tab is active.
,
Aug 28
For anyone who comes here via google/search. To restore old UI: chrome://flags/#top-chrome-md
,
Sep 5
I too would appreciate a fix. Previously, the omnibar background obeyed gtk.css. Now it doesn't. Having a whtite background when the rest of the page is dark can be a bit of a strain and distracting. Thank you!
,
Sep 12
,
Sep 17
,
Sep 17
,
Sep 26
https://askubuntu.com/questions/1072234/how-to-get-back-my-previous-omnibox-in-google-chrome-69-or-chromium-69 to this that want quick fix.
,
Sep 29
,
Oct 8
#15, the workaround is starting to break in dev/canary (buttons are misaligned), and long term I don't have hope that both UIs will be maintained. So it would be really nice if we at least get a confirmation that this is on the radar for the new UI.
,
Oct 24
Shouldn't this bug page be updated? We're now a few days into Chrome 70. I remember some years ago that the then project manager, Anthony Laforge, would punt the milestone involved. Here, we're still seeing M-69.
,
Nov 9
Here's at least someone from Google in favor of the dark side: https://www.youtube.com/watch?v=N_6sPd0Jd3g titled "Cost of a Pixel Color (Android Dev Summit '18)".
,
Nov 11
Kicking this to the omnibox triage queue. On Linux, when Chrome is in GTK mode, the omnibox colors should be sourced from the native theme. When it's in Chrome mode, they should be the default built-in colors. So if these users have set the Chrome settings to GTK mode, this is a bug.
,
Nov 12
Marking as available; sadly it appears no one will work on it in the next two months. Contributions welcome!
,
Nov 13
> So if these users have set the Chrome settings to GTK mode, this is a bug. Yes, they do have GTK mode.
,
Nov 27
The #top-chrome-md flag is gone in Version 72.0.3615.0, and there doesnt seem to be a replacement. I can live with some buttons being off position and hard to click, but i cant live with the glaring white omnibar.
,
Nov 27
I agree, the glaring white omnibar is very annoying on dark themes and even more with dark sites. I'm sorry, that I added no value to this thread, but I feel this thread is being ignored.
,
Nov 28
Per #21, > it appears no one will work on it in the next two months. Contributions welcome! If you have the time and energy to fix this, I'm sure everyone on this bug would appreciate it.
,
Nov 28
I'm sorry, I didn't notice that. My fault.
,
Dec 6
> The #top-chrome-md flag is gone in Version 72.0.3615.0, and there doesnt seem to be a replacement.
Am on stable 71.0.3578.80 and setting the flag #top-chrome-md to "default" doesn't revert the change anymore.
I am sorry to say this but this is really a miss! Please chromium devs, bring it back. I can't/wont use chromium as it is now (ugly).
Screenshots :
1- Before the change.
2- After the change.
,
Dec 7
,
Dec 7
Guys. Why need to use so biggest size for folders and bookmarks on bookmarks bar on desktop computers?
,
Dec 10
,
Dec 15
Issue 914338 has been merged into this issue.
,
Jan 12
The #top-chrome-md no longer works. The omnibar white background is really irritating, Plus the extra space that tab take up, the worst design chrome ever has. :(
,
Jan 20
(3 days ago)
Any news on this? It seems that Chrome v.72 will be released in 10 days, will we see a fix in this release?
,
Jan 20
(2 days ago)
Re. comment #33, probably not. I tested version 73.0.3664.3 and the omnibar background is still white.
,
Yesterday
(45 hours ago)
Come on Chromium! Google is starting to understand the importance both for people and energy of supporting dark themes - probably best not to have it's flagship browser unable to provide a dark omnibar except on a chrome book in incognito mode.
,
Today
(18 hours ago)
I won't upgrade to latest version unless Google fix this bug
,
Today
(15 hours ago)
Unfortunately they will just make it to where your favorite apps no longer function in the older version of chrome and you'll either have to switch browsers or upgrade unwillingly. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Jul 13