3 ms·
Why don't they fix the issues with the current UI that aren't GTK+s fault before they go and ditch it and introduce a whole new world of pain? As far as I can
by nly 13y ago
Why don't they fix the issues with the current UI that aren't GTK+s fault before they go and ditch it and introduce a whole new world of pain?
As far as I can tell, Chromium on Linux has been useless on high DPI screens since its inception. On my 15" laptop at 1920x1080 (just 140dpi) the fonts on browser tabs, and the tabs themselves, are too small and cannot be changed. I simply can't use the browser because of this.
Firefox, which has its own abstraction layer but uses janky old GTK+2 under the hood, does just fine.
I really don't care about extreme OpenGL rendering (laughable, aren't most accelerations disabled already due to driver whitelisting?) or the tiny fraction of the UI that is noticeably GTK+
- jeorgun 13y agoHigh-DPI support is coming with Aura (or, more accurately, being built on Aura; it looks like the high-DPI stuff will come slightly later): https://code.google.com/p/chromium/issues/detail?id=143619 https://code.google.com/p/chromium/issues/detail?id=143619
- finishingmove 13y agoGreat, but let's hope it doesn't start looking crap on regular DPI displays. You know, like those hipster websites that make your eyes bleed if you try to read them on anything other than a Retina display. "Most people I know use MacBooks anyway"
- hga 13y agoAt the same resolution on a 24" screen they're too small for my 80 year old father, and a bit hard on my eyes. A truly stunning oversight.
- kevingadd 13y agoChrome's not DPI aware on Windows either. I think they just don't care.