![]() ![]() If we measure letters themselves, number 32 is nowhere to be seen:ģ2 is not the width or height of a letter, neither is it a capital letter height, an x-letter height, an ascender height, a descender height. though I'd much prefer chromium or brave.What happens when you set "font_size": 32 in your favorite editor? I would’ve told you anyway, but I’m glad that you asked. So I guess I am stuck with firefox and edge for time to come. I asked here (again) because me experience is that here among the arch experts someone may have found a workaround using browser UIs CSS settings or a patch to the code base.Īll these standard environment variables and start parameters are known to me and I use them a lot - as, - as you said, - my needs are not the intended look for the desktop or a mix of differently scaling applications.īut all these are not unmanageable - but not being able to comfortably read the URL is a no go. If you google "tiny font address omni bar" you get many complaints, bug reports and feature requests related to this - some of which are mine. There is some hardcoding going on which chromium devs refuse to address. Brave, Vivaldi, Google Chrome - every single one of them cannot adjust the font of the address / omni / awesome bar individually. ![]() It's the same in every chromium based browser (with MS Edge being the only exception.). This is an outstanding bug that people complain about for more than 10 years. Has nothing to do with the system DPI scaling or the DPI scaling of the brwoser application itself. The UI scales correctly in tune with the system resulting in a tiny address bar font! The omnibar (address bar) font increases 30%īoth fonts having exactly the same relative proportional size to each other.Įither the UI gets huge as side effect of having a readable address bar or It doesn't matter which scaling factor you apply as BOTH fonts increase by 30% with 1.3 scaling. I am sorry, - I applaud your tenacity, but you are still missing my point: There is a clear difference in font weight though the system Roboto font is used. So what I am still looking for is a setting or workaround to get the exact same font size for menu items and text in the address bar (also collapsable tab list and so more.).īasically I need to scale the address bar font independent of the general UI font.Ī second annoyance is that the font in chromium or chrome looks lighter as the medium Roboto font I use everywhere else. You'll see that menues and web address clearly use a different font size. You can try yourself by testing with a ridiculous value like This proportion holds true with every setting for forced scaling. The address bar font is always (no matter the forced scale factor) about two thirds of the font size of the menu font. There is no problem to scale the chrome/chromium UI (including the adress-/omni-bar) to a factor of 131.25 % by starting the browser with the start parameterĬhromium -force-device-scale-factor=1.3125īut there seems to be a hardcoded value in the Chromium UI that scales the address-/omnibar font size smaller than the font used for menu items in the menu bar or in the context menues. Now coming back to this after a long time, - sorry for that, - I realize that I might not have stated my concern clearly. not sure I can be done.Īnyway - I just try to avoid chromium based browsers. But in a productive environment with multiple monitors and applications from different toolkits and versions? Sounds like a configuration nightmare. I see that this could work in a defined kiosk mode with only a very limited set of applications. The only way to avoid this would be the other way around - set the system font-sizes to match the chromium/chrome address bar font.Īnd then after that reduce the virtual resolution of the screen with randr until everything is big enough to be readable. It's a standing bug for way over ten years now and to my knowledge it can't be fixed with scaling the application itself - chromium hosts two sets of fonts: the fixed hardcoded ones and the others that adapt to the system environment. Having one or two font-sizes (tab titles and address bar) hardcoded is a clear design flaw. Sure bump up chromium scaling to 1.67 and I get a nice address bar font - but sadly now all other UI elements of chromium are way too big - 167% to be exact. The address bar font is only 60% of the system fonts? Regarding the chromium flags file - I tried that before even in combination with other scaling methods (also the suggested xrandr scaling from the arch wiki.) - but that creates new problems: You are probably right and it is worth doing everything with ranrd. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |