[SOLVED] Textbox Compressed Bug with Chrome

AugustineC · 2021-03-05 11:09:55

Hi guys. I think I am experiencing a very wierd bug on Chrome which may be caused by GTK application misconfigurations.

As you can see in this screenshot: https://www.dropbox.com/s/s3ia7wd41zsys … 8.png?dl=0

In the arch forum personal details page, all text boxes are just compressed together. However, this is not caused by a very thin window. Instead, I am using full screen mode on a 16:9 screen. Also, the reason why it is wierd is that I have not yet experienced this bug on other websites.

The reason why I classify this problem to Chrome is that I have also noticed that the "find" text box is also collapsed (https://www.dropbox.com/s/oyn8iz5pdoog1 … 2.png?dl=0), as shown in this screenshot, which is very annoying.

Is this some kind of GTK configuration bug? Thanks in advance for providing any suggestions.

Last edited by AugustineC (2021-03-09 07:44:13)

seth · 2021-03-05 14:57:44

The width of those boxes is constrained by the "size" and "maxlength" parameters rather than css.
Since you suspect gtk: which style do you use and does it happen w/ adwaita?

AugustineC · 2021-03-05 16:22:23

Hi seth,

Do you mean the GTK theme by word "style"? If so, I am using Mojave-Dark-Alt.

BTW, just as a clarification, the reason why I suspect GTK is that this problem appears after I changed some settings in GTK. More specifically, I changed the theme and some settings in /org/gnome/desktop/interface using dconf-editor, though I did not find any relevant field as you mentioned there.

Last edited by AugustineC (2021-03-05 16:23:31)

seth · 2021-03-05 16:25:09

Do you mean the GTK theme by word "style"?

Yes.

I am using Mojave-Dark-Alt.

And does it happen w/ adwaita (gnome default theme)?

AugustineC · 2021-03-05 16:29:52

Sorry, I am not quite sure what is meant by "happen w/ adwaita (gnome default theme)".

Based on my understanding, it should not be. The two themes should be separated.

As I am now seeing in the dconf, the only theme field seeming to be related to default theme is teh "gtk-key-theme" which stands for "Gtk+ Keybinding Theme". The value of this field is set to default.

Last edited by AugustineC (2021-03-05 16:32:45)

seth · 2021-03-05 16:44:01

https://wiki.archlinux.org/index.php/GTK#Themes

# quit chrome/chromium?
export GTK_THEME=Adwaita
chrome # or chromium?

It's important to launch chrome/chromium from the shell where you exported the theme variable.

AugustineC · 2021-03-05 17:08:39

Hi, I have used the following command, though it seems that the problem still persists.

Here is the screenshot: https://www.dropbox.com/s/64futiin9hd6n … t.png?dl=0

I am wondering if it is due to my wrong operation.

seth · 2021-03-05 21:07:47

No, looks reasonable.

I changed the theme and some settings in /org/gnome/desktop/interface using dconf-editor

So, what if you undo those changes? Does chrome return to proper behavior?
Which settings in particular did you change and to what values?

AugustineC · 2021-03-06 17:57:13

Hi, my appologies for replying late.

I think that I have already undone all the actions, but the problem persists. Here is a screenshot of current interface settings.

https://www.dropbox.com/s/hgj7r78t706xh … t.png?dl=0

Would you please check to see if there is any mistake? Thanks very much.

Last edited by AugustineC (2021-03-06 17:57:42)

seth · 2021-03-06 20:57:19

There's a leading dot before the default font?
Also the font name/size format is all over the place.
There's no size for the monospace font, a comma separated one for the default font and a blank separated for the document font key.

I have none of those keys and no idea which format is correct, but I'm pretty sure the leading "." is a typo and would simply try to remove all size values.
A quick google suggests the format is like "Font Name 10" and no quotes attached to the value.

AugustineC · 2021-03-07 09:15:50

Hi, thanks very much for helping!

The problem is finally solved after I changing the default font to "Lucida Grande, 10".

The problem is associated with the dot before the font type, though I am still confused by this: there indeed is quite a few fonts which start with a dot in font management in system settings. Also, I have used those fonts starting with dot in other applications, and it works fine.

seth · 2021-03-07 12:09:18

Just becase some™ fonts (really?) start their name with a dot doesn't mean you can randomly throw that in somewhere.
For font names, try

fc-list | grep some_pattern

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

AugustineC · 2021-03-09 07:43:38

Hi thanks for your reply! I will do that immediately.

Arch Linux

#1 2021-03-05 11:09:55

[SOLVED] Textbox Compressed Bug with Chrome

#2 2021-03-05 14:57:44

Re: [SOLVED] Textbox Compressed Bug with Chrome

#3 2021-03-05 16:22:23

Re: [SOLVED] Textbox Compressed Bug with Chrome

#4 2021-03-05 16:25:09

Re: [SOLVED] Textbox Compressed Bug with Chrome

#5 2021-03-05 16:29:52

Re: [SOLVED] Textbox Compressed Bug with Chrome

#6 2021-03-05 16:44:01

Re: [SOLVED] Textbox Compressed Bug with Chrome

#7 2021-03-05 17:08:39

Re: [SOLVED] Textbox Compressed Bug with Chrome

#8 2021-03-05 21:07:47

Re: [SOLVED] Textbox Compressed Bug with Chrome

#9 2021-03-06 17:57:13

Re: [SOLVED] Textbox Compressed Bug with Chrome

#10 2021-03-06 20:57:19

Re: [SOLVED] Textbox Compressed Bug with Chrome

#11 2021-03-07 09:15:50

Re: [SOLVED] Textbox Compressed Bug with Chrome

#12 2021-03-07 12:09:18

Re: [SOLVED] Textbox Compressed Bug with Chrome

#13 2021-03-09 07:43:38

Re: [SOLVED] Textbox Compressed Bug with Chrome

Board footer