Ttgjyuk

What does it mean to make a bootable LiveUSB?

How could a female member of a species produce eggs unto death?

Is it true that real estate prices mainly go up?

Can the damage from a Talisman of Pure Good (or Ultimate Evil) be non-lethal?

How could a scammer know the apps on my phone / iTunes account?

Why would a flight no longer considered airworthy be redirected like this?

Why using two cd commands in bash script does not execute the second command

Life insurance that covers only simultaneous/dual deaths

Dot in front of file

What has been your most complicated TikZ drawing?

I need to drive a 7/16" nut but am unsure how to use the socket I bought for my screwdriver

Do I need life insurance if I can cover my own funeral costs?

Instead of Universal Basic Income, why not Universal Basic NEEDS?

Happy pi day, everyone!

PlotLabels with equations not expressions

Why did it take so long to abandon sail after steamships were demonstrated?

What options are left, if Britain cannot decide?

What are the possible solutions of the given equation?

Can elves maintain concentration in a trance?

Identifying the interval from A♭ to D♯

Is it possible that AIC = BIC?

The use of "touch" and "touch on" in context

Why must traveling waves have the same amplitude to form a standing wave?

How to deal with a cynical class?

How to get back my previous omnibox in Google Chrome 69 or Chromium 69?

Chrome dark adress bar (omnibox)Ubuntu 16.04 and Chrome address bar highlight colorChrome UI styles are not working under Ubuntu! GTK Theme is not working!browser compositor issues - chromium versus chromexdg-open: chrome/chromium/operaHow to add Chrome Apps to the Ubuntu Launcher with iconsGoogle chrome and ChromiumChromium/Chrome UI Font ErrorGmail is showing “This version of Chrome is no longer supported”Text size in Chrome's omnibar is too smallHow can I start a separate instance (not profile) of Chromium, with its own icon?Why Chrome apps/windows do not follow GTK theme?

4

2

For several versions in recent past, the color of the omnibox in Google Chrome (and Chromium) was determined by the user's gtk3 theme (if the user opted for using a gtk theme instead of classic mode in chrome://settings.

This held true until the release of version 69 in which the omnibox now looks like this:

How can I restore the omnibox to its previous appearance in Google Chrome 68 that looks like this?

google-chrome chromium

share|improve this question

edited Sep 6 '18 at 16:09

DK Bose

asked Sep 5 '18 at 6:08

DK BoseDK Bose

14.4k124286

add a comment | 

4

2

For several versions in recent past, the color of the omnibox in Google Chrome (and Chromium) was determined by the user's gtk3 theme (if the user opted for using a gtk theme instead of classic mode in chrome://settings.

This held true until the release of version 69 in which the omnibox now looks like this:

How can I restore the omnibox to its previous appearance in Google Chrome 68 that looks like this?

google-chrome chromium

share|improve this question

edited Sep 6 '18 at 16:09

DK Bose

asked Sep 5 '18 at 6:08

DK BoseDK Bose

14.4k124286

add a comment | 

For several versions in recent past, the color of the omnibox in Google Chrome (and Chromium) was determined by the user's gtk3 theme (if the user opted for using a gtk theme instead of classic mode in chrome://settings.

This held true until the release of version 69 in which the omnibox now looks like this:

How can I restore the omnibox to its previous appearance in Google Chrome 68 that looks like this?

google-chrome chromium

share|improve this question

edited Sep 6 '18 at 16:09

DK Bose

asked Sep 5 '18 at 6:08

DK BoseDK Bose

14.4k124286

share|improve this question

edited Sep 6 '18 at 16:09

DK Bose

asked Sep 5 '18 at 6:08

DK BoseDK Bose

14.4k124286

share|improve this question

edited Sep 6 '18 at 16:09

DK Bose

asked Sep 5 '18 at 6:08

DK BoseDK Bose

14.4k124286

asked Sep 5 '18 at 6:08

DK BoseDK Bose

14.4k124286

asked Sep 5 '18 at 6:08

DK BoseDK Bose

14.4k124286

1 Answer
1

active

oldest

votes

5

See update at the bottom of this answer

Edit: the workaround described below was limited to version 69 and 70. It is not possible to circumvent the white background of the address bar in version 71.

Further edit: the relevant bug has now been taken up by a Googler who worked extensively on the transition of Chrome to gtk3 and so I'm hopeful of a solution soon.

---

Enter chrome://flags/#top-chrome-md in the omnibox and press Enter.

Click on the dropdown in the first entry, choose "Normal" and restart the browser.

It will change appearance from default

to normal

Note that flags may disappear at any time in the future. However, a bug, GTK+ theme ignored in omnibar in the new interface has been filed and, if addressed, may provide a solution without resorting to chrome://flags.

Update: This bug has not attracted sufficient interest and currently, 20181205, nobody is assigned to it. And the workaround fails in Chrome 71.

Update 20190315:

With Chrome 73, one can use --enable-features=WebUIDarkMode --force-dark-mode after making sure that the Classic theme option is chosen in Settings > Appearance instead of GTK+. Launched in this way, Google Chrome uses a built-in dark mode that doesn't rely on or use your GTK theme colors. As of now, dropdowns such as that of bookmark folders or the ☰ icon also reflect the dark mode. (The browser's internal pages accessed by chrome:// are unaffected.)

share|improve this answer

edited 1 hour ago

answered Sep 5 '18 at 6:16

DK BoseDK Bose

14.4k124286

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1072234%2fhow-to-get-back-my-previous-omnibox-in-google-chrome-69-or-chromium-69%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

5

See update at the bottom of this answer

Edit: the workaround described below was limited to version 69 and 70. It is not possible to circumvent the white background of the address bar in version 71.

Further edit: the relevant bug has now been taken up by a Googler who worked extensively on the transition of Chrome to gtk3 and so I'm hopeful of a solution soon.

---

Enter chrome://flags/#top-chrome-md in the omnibox and press Enter.

Click on the dropdown in the first entry, choose "Normal" and restart the browser.

It will change appearance from default

to normal

Note that flags may disappear at any time in the future. However, a bug, GTK+ theme ignored in omnibar in the new interface has been filed and, if addressed, may provide a solution without resorting to chrome://flags.

Update: This bug has not attracted sufficient interest and currently, 20181205, nobody is assigned to it. And the workaround fails in Chrome 71.

Update 20190315:

With Chrome 73, one can use --enable-features=WebUIDarkMode --force-dark-mode after making sure that the Classic theme option is chosen in Settings > Appearance instead of GTK+. Launched in this way, Google Chrome uses a built-in dark mode that doesn't rely on or use your GTK theme colors. As of now, dropdowns such as that of bookmark folders or the ☰ icon also reflect the dark mode. (The browser's internal pages accessed by chrome:// are unaffected.)

share|improve this answer

edited 1 hour ago

answered Sep 5 '18 at 6:16

DK BoseDK Bose

14.4k124286

add a comment | 

5

See update at the bottom of this answer

Edit: the workaround described below was limited to version 69 and 70. It is not possible to circumvent the white background of the address bar in version 71.

Further edit: the relevant bug has now been taken up by a Googler who worked extensively on the transition of Chrome to gtk3 and so I'm hopeful of a solution soon.

---

Enter chrome://flags/#top-chrome-md in the omnibox and press Enter.

Click on the dropdown in the first entry, choose "Normal" and restart the browser.

It will change appearance from default

to normal

Note that flags may disappear at any time in the future. However, a bug, GTK+ theme ignored in omnibar in the new interface has been filed and, if addressed, may provide a solution without resorting to chrome://flags.

Update: This bug has not attracted sufficient interest and currently, 20181205, nobody is assigned to it. And the workaround fails in Chrome 71.

Update 20190315:

With Chrome 73, one can use --enable-features=WebUIDarkMode --force-dark-mode after making sure that the Classic theme option is chosen in Settings > Appearance instead of GTK+. Launched in this way, Google Chrome uses a built-in dark mode that doesn't rely on or use your GTK theme colors. As of now, dropdowns such as that of bookmark folders or the ☰ icon also reflect the dark mode. (The browser's internal pages accessed by chrome:// are unaffected.)

share|improve this answer

edited 1 hour ago

answered Sep 5 '18 at 6:16

DK BoseDK Bose

14.4k124286

add a comment | 

See update at the bottom of this answer

Edit: the workaround described below was limited to version 69 and 70. It is not possible to circumvent the white background of the address bar in version 71.

Further edit: the relevant bug has now been taken up by a Googler who worked extensively on the transition of Chrome to gtk3 and so I'm hopeful of a solution soon.

---

Enter chrome://flags/#top-chrome-md in the omnibox and press Enter.

Click on the dropdown in the first entry, choose "Normal" and restart the browser.

It will change appearance from default

to normal

Note that flags may disappear at any time in the future. However, a bug, GTK+ theme ignored in omnibar in the new interface has been filed and, if addressed, may provide a solution without resorting to chrome://flags.

Update: This bug has not attracted sufficient interest and currently, 20181205, nobody is assigned to it. And the workaround fails in Chrome 71.

Update 20190315:

With Chrome 73, one can use --enable-features=WebUIDarkMode --force-dark-mode after making sure that the Classic theme option is chosen in Settings > Appearance instead of GTK+. Launched in this way, Google Chrome uses a built-in dark mode that doesn't rely on or use your GTK theme colors. As of now, dropdowns such as that of bookmark folders or the ☰ icon also reflect the dark mode. (The browser's internal pages accessed by chrome:// are unaffected.)

share|improve this answer

edited 1 hour ago

answered Sep 5 '18 at 6:16

DK BoseDK Bose

14.4k124286

share|improve this answer

edited 1 hour ago

answered Sep 5 '18 at 6:16

DK BoseDK Bose

14.4k124286

answered Sep 5 '18 at 6:16

DK BoseDK Bose

14.4k124286

answered Sep 5 '18 at 6:16

DK BoseDK Bose

14.4k124286